On 2013-06-27T12:40:49, Dejan Muhamedagic <[email protected]> wrote:
> > It would be nice to have an intelligent "patcher" which takes one CIB
> > snapshot at the beginning of edit, than generates a diff and looks if it
> > applies to a current CIB cleanly (all except epoch). Then it would be
> > possible to use current epoch in a diff which goes to a cib daemon.
> > I do not know does it make a sense.
> Yes, it does. I just wonder how much performance would be
> affected.
Would be nice if cibadmin had an option to test applying a patch,
similar to patch --dry-run.
Of course, while the performance may exist, it's still a bit "racy":
even between the dry-run and the final application, the CIB could
change. (Basically, people changing configuration without sync on
multiple nodes is bound to eventually clash.)
But we could warn if the epoch has changed, and then ask to try to
commit w/o the epoch change? (Or maybe just do that automatically.)
Regards,
Lars
--
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB
21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
