[Linux-HA] Change the cib.xml under a live cluster

[Andrew Beekhof]

Please never, never ever, not in a million years, change the cib.xml
file when the cluster is active.

We specifically try to detect this, thats how bad an idea it is.

If you want to edit the XML by hand, please get a copy of it by running:
    cibadmin -Q > ~/saved.cib.xml

then you may safely edit ~/saved.cib.xml and (when you're ready)
upload it again with:
    cat ~/saved.cib.xml | cibadmin -R (plus any other options you want to add)

WARNING: continuing to edit the live cib.xml file while the cluster is
running may result in me tracking you down and hitting you over the
head with a large hammer :)

On 11/2/06, Andreas Kurz <akurz at sms.at> wrote:
>
> > On a live cluster, I can change or modify the cib.xml file (and becouse
> > I modify it I must delete the other files in /var/lib/heartbeat/crm/
> > directory) and update the CIB with the "cat cib.xml | cibadmin -R -o
> > resources".
>
> no, no ... the changes take effect immediately and are propagated to all
> nodes. it's best practice to verify the changes with "crm_verify -VX
> yourchangedresources.xml" before an update with e.g. "cibadmin
> --obj_type resources -R -x yourchangedresources.xml".
>
> > And the another:
> > When the heartbeat will restart, it will parse the new cib.xml (which i
> > modified) and will work fine with the new resources.
>
> of course, if you modify the cib.xml when the heartbeat cluster is
> completely down. it is not advisable to manipulate the cib.xml by hand
> when the cluster is online.
> _______________________________________________
> Linux-HA mailing list
> Linux-HA at lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>