Just started a new topic.
>The cibadmin wouldn't complain about a missing interval. The DTD
>says nothing about that. The CRM could, not sure about that.
>The CLI is also not checking that. It may do so in future, not
>decided yet about it, as it may prove to be too difficult.
Please explain this:
$cat ip.xml
<primitive id="myIP" class="ocf" type="IPaddr" provider="heartbeat">
<instance_attributes id="myIP_attributes">
<nvpair id="myIP_ip" name="ip" value="192.168.1.130"/>
</instance_attributes>
<operations>
<op id="monitor_myIP" name="monitor" interval="30s"
timeout="30s"/> <op id="start_myIP" interval="30s"
name="start" timeout="30s"/>
<op id="stop_myIP" interval="30s" name="stop" timeout="30s"/>
</operations>
</primitive>
$ cibadmin -VR -x ip.xml
cibadmin[18497]: 2008/09/09_23:30:56 info: main: Starting mainloop
cibadmin[18497]: 2008/09/09_23:30:58 info: cibadmin_op_callback: Call passed
$ cat ip2.xml
<primitive id="myIP" class="ocf" type="IPaddr" provider="heartbeat">
<instance_attributes id="myIP_instance_attributes">
<nvpair id="myIP_ip" name="ip" value="192.168.1.130"/>
</instance_attributes>
<operations>
<op name="monitor" interval="30s" id="myIP_monitor" timeout="30s"/>
<op name="start" id="myIP_start" timeout="30s"/>
<op name="stop" id="myIP_stop" timeout="30s"/>
</operations>
</primitive>
$ cibadmin -VR -x ip2.xml
cibadmin[18501]: 2008/09/09_23:31:37 info: main: Starting mainloop
cibadmin[18501]: 2008/09/09_23:31:38 WARN: cibadmin_op_callback: Call
cib_replace failed (-47): Update does not conform to the configured
schema/DTD
Call cib_replace failed (-47): Update does not conform to the
configured schema/DTD
<null>
Pacemaker 0.7 + Heartbeat 2.99
--
Serge Dubrouski.
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
