>> clones have only meta_attributes, so move the two nvpairs over there. <<
Oh. That's the bit I missed in the documentation, then. Yes, once that's sorted the cib swallows this update without the barest hint of a complaint. Thank you!! (I'm sure you hear it so often that you can't hear it anymore, but I still have to say: this clustering software *rocks*; I'm not sure there's a cooler, more significant enterprise class project, short of the kernel itself, anywhere.) Be well, Karl On Wed, Aug 19, 2009 at 6:56 AM, Dejan Muhamedagic <[email protected]>wrote: > Hi, > > On Wed, Aug 19, 2009 at 06:27:32AM -0400, Karl W. Lewis wrote: > > On Mon, Aug 10, 2009 at 2:20 PM, Karl W. Lewis <[email protected] > >wrote: > > > > > D'oh! > > > > > > Yes, it's Pacemaker 1.0.3 I should have said so. > > > > > > I am sorry for what turns out to be a[nother] the stupid question. > Thank > > > you for your kind patience. > > > > > > Be well, > > > > > > Karl > > > > > > > > > On Mon, Aug 10, 2009 at 1:50 PM, Dejan Muhamedagic < > [email protected]>wrote: > > > > > >> Hi, > > >> > > >> On Mon, Aug 10, 2009 at 12:54:44PM -0400, Karl W. Lewis wrote: > > >> > I have used cibadmin to add contraints to a running cluster, but now > I > > >> wish > > >> > to add another resource, a stonith configuration, to my cluster. > > >> > > >> I guess that this is pacemaker 1.0. > > >> > > >> > The snippet of xml I am trying to feed the cluster looks like this: > > >> > >>>> > > >> > <resources> > > >> > <clone id="DoFencing"> > > >> > <meta_attributes id = "DoFencing_options"> > > >> > <nvpair id="DoFencing_option-1" name="globally-unique" > > >> value="false"/> > > >> > </meta_attributes> > > >> > <instance_attributes> > > >> > <nvpair name="clone_max" value="3"/> > > >> > <nvpair name="clone_node_max" value="1"/> > > >> > > >> Both are missing id. Also, replace "_" with "-". > > >> > > >> > </instance_attributes> > > >> > <primitive id="child_DoFencing" class="stonith" > > >> type="external/egenera" > > >> > provider="heartbeat"> > > >> > <operations> > > >> > <op name="monitor" interval="400s" timeout="200s" > > >> prereq="nothing"/> > > >> > > >> Missing id. "prereq" is now named "requires". > > >> > > >> Thanks, > > >> > > >> Dejan > > >> > > >> > </operations> > > >> > <instance_attributes id="egenera-parameters"> > > >> > <nvpair id="egenera-parameter-1" name="hostlist" > > >> value="wsc-voo-205, > > >> > wsc-voo-206, wsc-voo-207"/> > > >> > </instance_attributes> > > >> > </primitive> > > >> > </clone> > > >> > </resources> > > >> > > > >> > <<<< > > >> > > > >> > >>> > > >> > cibadmin -V -V -V -V -V -V -V -C -o resources -x > stonith_production.xml > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: debug2: main: Option o > => > > >> > resources > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: debug2: main: Option x > => > > >> > stonith_production.xml > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: log_data_element: main: > > >> [admin > > >> > input] <resources > > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: log_data_element: main: > > >> [admin > > >> > input] <clone id="DoFencing" > > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: log_data_element: main: > > >> [admin > > >> > input] <meta_attributes id="DoFencing_options" > > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: log_data_element: main: > > >> [admin > > >> > input] <nvpair id="DoFencing_option-1" name="globally-unique" > > >> > value="false" /> > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: log_data_element: main: > > >> [admin > > >> > input] </meta_attributes> > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: log_data_element: main: > > >> [admin > > >> > input] <instance_attributes > > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: log_data_element: main: > > >> [admin > > >> > input] <nvpair name="clone_max" value="3" /> > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: log_data_element: main: > > >> [admin > > >> > input] <nvpair name="clone_node_max" value="1" /> > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: log_data_element: main: > > >> [admin > > >> > input] </instance_attributes> > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: log_data_element: main: > > >> [admin > > >> > input] <primitive id="child_DoFencing" class="stonith" > > >> > type="external/egenera" provider="heartbeat" > > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: log_data_element: main: > > >> [admin > > >> > input] <operations > > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: log_data_element: main: > > >> [admin > > >> > input] <op name="monitor" interval="400s" timeout="200s" > > >> > prereq="nothing" /> > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: log_data_element: main: > > >> [admin > > >> > input] </operations> > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: log_data_element: main: > > >> [admin > > >> > input] <instance_attributes id="egenera-parameters" > > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: log_data_element: main: > > >> [admin > > >> > input] <nvpair id="egenera-parameter-1" name="hostlist" > > >> > value="wsc-voo-205, wsc-voo-206, wsc-voo-207" /> > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: log_data_element: main: > > >> [admin > > >> > input] </instance_attributes> > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: log_data_element: main: > > >> [admin > > >> > input] </primitive> > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: log_data_element: main: > > >> [admin > > >> > input] </clone> > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: log_data_element: main: > > >> [admin > > >> > input] </resources> > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: > > >> > init_client_ipc_comms_nodispatch: Attempting to talk on: > > >> /var/run/crm/cib_rw > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: debug3: > > >> > init_client_ipc_comms_nodispatch: Processing of /var/run/crm/cib_rw > > >> complete > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: > > >> > init_client_ipc_comms_nodispatch: Attempting to talk on: > > >> > /var/run/crm/cib_callback > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: debug3: > > >> > init_client_ipc_comms_nodispatch: Processing of > > >> /var/run/crm/cib_callback > > >> > complete > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: cib_native_signon_raw: > > >> > Connection to CIB successful > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: debug3: > > >> cib_native_perform_op: > > >> > Sending cib_create message to CIB service > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: debug3: > > >> cib_native_perform_op: > > >> > Message sent > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: debug3: > > >> cib_native_perform_op: > > >> > Async call, returning > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: debug3: main: cibadmin > > >> waiting > > >> > for reply from the local CIB > > >> > cibadmin[18807]: 2009/08/10_12:44:17 info: main: Starting mainloop > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: debug2: > cib_native_callback: > > >> > Invoking callback cibadmin_op_callback for call 2 > > >> > cibadmin[18807]: 2009/08/10_12:44:17 WARN: cibadmin_op_callback: > Call > > >> > cib_create failed (-47): Update does not conform to the configured > > >> > schema/DTD > > >> > Call cib_create failed (-47): Update does not conform to the > configured > > >> > schema/DTD > > >> > <null> > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: debug3: > cib_native_msgready: > > >> No > > >> > message pending > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: cib_native_signoff: > Signing > > >> out > > >> > of the CIB Service > > >> > cibadmin[18807]: 2009/08/10_12:44:17 debug: debug3: main: cibadmin > > >> exiting > > >> > normally > > >> > <<< > > >> > > > >> > The log says: > > >> > >> > > >> > cib[4164]: 2009/08/10_12:44:17 ERROR: Element instance_attributes > failed > > >> to > > >> > validate content > > >> > > > >> > cib[4164]: 2009/08/10_12:44:17 ERROR: Extra element > instance_attributes > > >> in > > >> > interleave > > >> > > > >> > cib[4164]: 2009/08/10_12:44:17 ERROR: Element clone failed to > validate > > >> > content > > >> > > > >> > cib[4164]: 2009/08/10_12:44:17 ERROR: Element resources has extra > > >> content: > > >> > group > > >> > > > >> > cib[4164]: 2009/08/10_12:44:17 ERROR: Invalid sequence in interleave > > >> > > > >> > cib[4164]: 2009/08/10_12:44:17 ERROR: Element cib failed to validate > > >> content > > >> > > > >> > cib[4164]: 2009/08/10_12:44:17 WARN: cib_perform_op: Updated CIB > does > > >> not > > >> > validate against pacemaker-1.0 schema/dtd > > >> > cib[4164]: 2009/08/10_12:44:17 WARN: cib_diff_notify: Update > (client: > > >> > cibadmin, call:2): 0.154.17 -> 0.155.1 (Update does not conform to > the > > >> > configured schema/DTD) > > >> > cib[4164]: 2009/08/10_12:44:17 WARN: cib_process_request: Operation > > >> > complete: op cib_create for section resources > (origin=local/cibadmin/2, > > >> > version=0.154.17): Updat > > >> > e does not conform to the configured schema/DTD (rc=-47) > > >> > << > > >> > > > >> > The reference to "group" doesn't make sense to me, except that my > > >> cluster > > >> > resourdces as currently configured include a group of resources that > > >> must > > >> > stay together, (a disk to mount and an IP address). > > >> > > > >> > Is it obvious what I am doing wrong? > > >> > > > >> > Thanks, > > >> > > > >> > Karl > > >> > _______________________________________________ > > >> > 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 > > >> > > > > > > It is with considerable trepidation that I repeat my question... I > think > > I've fixed all my typos, but the cluster assures me that the "update does > > not conform to the configured scheme/DTD" > > > > This is the fragment I'm trying to add by: `cibadmin -C -o resources -x > > cib_stonith.xml` > > > > <resources> > > <clone id="DoFencing"> > > <meta_attributes id = "DoFencing_options"> > > <nvpair id="DoFencing_option-1" name="globally-unique" > > value="false"/> > > </meta_attributes> > > <instance_attributes> > > <nvpair id="clone-max-value" name="clone-max" value="3"/> > > <nvpair id="clone-node-max-value" name="clone-node-max" > > value="1"/> > > </instance_attributes> > > clones have only meta_attributes, so move the two nvpairs over > there. Sorry, missed that one last time. BTW, you can also use > the crm shell. > > Thanks, > > Dejan > > > <primitive id="child_DoFencing" class="stonith" > > type="external/egenera" > > > <operations> > > <op id="Fencing_Monitor" name="monitor" interval="400s" > > timeout="200s" requires="nothing"/> > > </operations> > > <instance_attributes id="egenera-parameters"> > > <nvpair id="egenera-parameter-1" name="hostlist" > value="host1, > > host2, host3"/> > > </instance_attributes> > > </primitive> > > </clone> > > </resources> > > > > Is there some other way to add this? I mean, is the command the wrong > one? > > Do I need to have a <cib> header? Is it the case that one can't add > > resources piecemeal? I've tried with and without the <resources> tags > > > > I managed to add a location constraint without trouble, it lloked like > this: > > > > <constraints> > > <rsc_location id="run_WebServer_Group" rsc="WebServer_Group" > > node="host1" score="100"/> > > </constraints> > > > > The command was just `cibadmin -C -o contraints -x location.xml` and that > > just worked. > > > > This is heartbeat 2.99.2-8.1.i386 for RHEL 5.2, and pacemaker > > 1.0.3-2.2.i386. > > > > Thanks, > > > > Karl > > _______________________________________________ > > 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 > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
