On Jan 8, 2008, at 9:38 AM, Jergen Dutch wrote:
Hello,
Happy New Year! This year I switched over to heartbeat 2. I like it,
but find the xml configuration file terrifying and ugly.
There was supposed to be a nice gui to hide all that :-(
I was reading the heartbeat blog today and it got me thinking:
"This can be really annoying and can easily result in system
administrators[3] making mistakes either in the middle of the night,
or when under pressure"
I find managing the xml files with heartbeat 2 *horrible*. The
software is really nice, but every time I have to deal with xml I want
to poke my eyes out with a rabid shark.
The excellent haresources2cib.py script handles conversion of
haresources at the start, but all changes from then on need to be in
xml.
There are some nice helper tools for modifying node and resource
attributes (eg. crm_attribute and crm_resource).
There is also crm_primitive.py for adding new resources (and the
associated constraints).
The xml isn't always pretty, but 90% of the time one is just filling
in a template which, as crm_primitive shows, can be easily scripted.
The docs give examples, e.g.:
Here is an example of adding a resource to the CIB:
cibadmin -C -o resources -X '<primitive id="WebServerIP" class="ocf"
type="IPaddr" provider="heartbeat">
<instance_attributes>
<attributes>
<nvpair id="WebServerIP_ip" name="ip" value="127.0.0.26"/>
</attributes>
</instance_attributes>
</primitive>'
A few questions:
1. Without restarting or shutting down the cluster, and without
editing the cib.xml file how can I make a change to the cluster
configuration (i.e. how can I use haresources2cib.py to generate an
updated cib.xml and get the cluster to use it without a restart)
2. How can I override the defaults (such as timeout) in the resulting
cib.xml file?
Thanks a lot.
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
