On 4/19/07, Doug Knight <[EMAIL PROTECTED]> wrote:
After a closer look at the DTD and my xml file, I found two things: 1) I had rsc_location where I should have had rsc_colocatioon, which is why crm_verify was choking on the lack of an rsc; and 2) I can only have one constraint (rsc_colocation, rsc_order, etc) per file.
you can have more, but then you need to put them inside a <constraints> object. XML can only have one root object
Once I made these changes, crm_verify passed the xml. I'm going to add them to the cib.xml via cibadmin now. Doug On Thu, 2007-04-19 at 10:50 -0400, Doug Knight wrote: > Hi Serge, > I tried using cibadmin, and I'm getting a message "Call cib_create > failed (-23): Activation Failed" when I try to execute the following: > > cibadmin -o constraints -C -x rule_fs_on_drbd_stopped.xml > > I've attached the current cib.xml and the rule_fs_drbd_stopped.xml > files. What does the activation failed mean? Its similar to the error I > would get occasionally when trying to add constraints via the GUI. > > Doug > > On Wed, 2007-04-18 at 23:14 +0200, Serge Dewailly wrote: > > > Hi, > > > > I think easier and more safe using the cibadmin tool. > > I prepare separate file for resources, constraints and crm_config, and > > then import them into cib using : > > cibadmin -o resources -C -x resource_file.xml > > replace -C by -R to replace, -D to delete > > > > The advantage, in my opinion, is you can see the changes / effect in the > > log in real time (tail -f) > > Also, the dtd strucure is verified before inserting in the cib, which > > prevents disaster on the whole node... > > > > Serge > > > > Doug Knight a écrit : > > > I don't think so, at least I have not found a way. Which bears my next > > > question, what is the recommended method/procedure for making changes to > > > the cib.xml? Editor or cibadmin? Are there more examples of using > > > cibadmin then what's on the web site? > > > > > > Doug > > > On Wed, 2007-04-18 at 11:44 -0700, Alastair N. Young wrote: > > > > > > > > >> Can the role=Master in the rsc_location be configured via the gui? If > > >> so, how? > > >> > > >> I'm running heartbeat 2.0.7 on CentOS 4.4 > > >> > > >> Alastair Young > > >> Director, Operations > > >> Ludi labs > > >> 399 West El Camino Real > > >> Mountain View, CA 94040 > > >> Email: [EMAIL PROTECTED] > > >> Direct: 650-241-0068 > > >> Mobile: 925-784-0812 > > >> > > >> -----Original Message----- > > >> From: [EMAIL PROTECTED] > > >> [mailto:[EMAIL PROTECTED] On Behalf Of Alan Robertson > > >> Sent: Tuesday, April 17, 2007 11:24 AM > > >> To: General Linux-HA mailing list > > >> Subject: Re: [Linux-HA] Cannot create group containing drbd using HB GUI > > >> > > >> Lars Marowsky-Bree wrote: > > >> > > >>> On 2007-04-17T07:59:29, Serge Dewailly <[EMAIL PROTECTED]> > > >>> > > >> wrote: > > >> > > >>>> Hi, > > >>>> > > >>>> You can choose the default primary node for drbd by fixing > > >>>> > > >> constraints. > > >> > > >>>> For exemple > > >>>> <rsc_location id="drbd1_loc_nodeA" rsc="drbd1"> > > >>>> <rule id="pref_drbd1_loc_nodeA" score="600"> > > >>>> <expression attribute="#uname" operation="eq" value="nodeA" > > >>>> id="pref_drbd1_loc_nodeA_attr"/> > > >>>> </rule> > > >>>> <rule id="pref_drbd1_loc_nodeB" score="800"> > > >>>> <expression attribute="#uname" operation="eq" value="nodeB" > > >>>> id="pref_drbd1_loc_nodeB_attr"/> > > >>>> </rule> > > >>>> </rsc_location> > > >>>> > > >>>> In this case, nodeB will be primary for resource drbd1. Is that what > > >>>> > > >> you > > >> > > >>>> were looking for ? > > >>>> > > >>> Not like this, not when using the drbd OCF Resource Agent as a > > >>> master-slave one. In that case, you need to bind the rsc_location to > > >>> > > >> the > > >> > > >>> role=Master as well. > > >>> > > >> I was missing this in the CIB idioms page. I just added it. > > >> > > >> http://linux-ha.org/CIB/Idioms > > >> http://linux-ha.org/CIB/Idioms/MasterConstraints > > >> > > >> > > >> > > > _______________________________________________ > > > Linux-HA mailing list > > > Linux-HA@lists.linux-ha.org > > > http://lists.linux-ha.org/mailman/listinfo/linux-ha > > > See also: http://linux-ha.org/ReportingProblems > > > > > > > > _______________________________________________ > > Linux-HA mailing list > > Linux-HA@lists.linux-ha.org > > http://lists.linux-ha.org/mailman/listinfo/linux-ha > > See also: http://linux-ha.org/ReportingProblems > > > _______________________________________________ > Linux-HA mailing list > Linux-HA@lists.linux-ha.org > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
_______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
