dknight at wsi
Jul 11, 2008, 8:36 AM
Post #1 of 1
(78 views)
Permalink
|
|
Best practice for CIB XML automated updates
|
|
All,
For our project I have developed a number of tools that allow us to
regularly build, install, and test our applications in a fully automated
way. I am now looking at automating changes to the heartbeat XML for
adding/updating/deleting resources, constraints, etc. I was wondering if
anyone had a best practice for this kind of update. What I'm looking for
is:
1. Which commands do you use to add, update, delete, as there are
at least a couple of different ways of doing these functions (cibadmin,
crm_resource, etc, and cibadmin has -R, -U and -M, which their
differences are not clear)
2. Do you maintain each resource, constraint, etc in a separate xml
file?
3. How do you handle the actual changes, i.e. do you precheck to
see if the resource already exists, if a resource name is changing how
do you handle removing the old one, etc? Does heartbeat care if you
simply update everything, even if its not changing?
The goal is to allow a developer to use a template of xml, plugin their
names, etc, and submit it to our CM system. The automated process pulls
this out and takes care of putting it on the correct test system and
invoking the proper commands to update the CIB.
Thanks,
Doug Knight
WSI Corp
_______________________________________________
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
|
