Bug 15912

Summary:	Automated configuration migration
Product:	[Retired] Red Hat High Availability Server	Reporter:	David D.W. Downey <david.downey>
Component:	piranha	Assignee:	Phil Copeland <copeland>
Status:	CLOSED DEFERRED	QA Contact:	Phil Copeland <copeland>
Severity:	medium	Docs Contact:
Priority:	low
Version:	1.0	Keywords:	FutureFeature
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2000-08-10 08:55:56 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Red Hat Bugzilla 2000-08-10 08:55:54 UTC

Problem:   Changes to the active node's configuration file (lvs.cf) does not automatically migrate to backup node's configuration file.

Case:         I add a new  real server to the pool or create a new virtual server entry, I have to hand copy the lvs.cf file to the backup node, restart 
everything for LVS on the backup node AFTER restarting the change on the active node of the LVS front end. 

Possible enhancement: Could some sort of automation method be put in place to check for changes (diff or something) and migrate the 
change to the backup? Could even set it so that you HAVE to make the change on the active node for the change to propagate.

Comment 1 Red Hat Bugzilla 2000-08-10 18:58:43 UTC

Yes, this is noted in the documentation also.

Automatic copying of the configuration file is planned for the next product
release (it was actually in THIS release, but got pulled at the last minute due
insufficient time for security testing), with future releases after that having
even greater enhanced cluster sync'ing and restarting.

If we are able to provide it in an earlier timeframe, updated RPMs will be
announced and posted on the web site.