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.
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.