Am Donnerstag, 15. Mai 2008 11:03 schrieb Adrian Chapela: (...) > This was I think. I don't use GUI, I edit the cib.xml file and in my > tests I saw the resources write order affects to constraints (or vice > versa, I don't know exactly).
I hope you do NOT edit your cib.xml directly, but use cibadmin to pass the changes you did in a copy of the cib to the CRM. > > You can test it with: > > <resources> > <group id="FW_GROUP"> (... a lot of resources. deleted for readability) > </group> > <clone id="pingd"> (...) > </clone> > </resources> > > > <constraints> > <rsc_order id="order_transition_1" from="tunnel_vf1" > action="start" type="before" to="tunnel_vf2"/> (... more constratins) > </constraints> > > If you use this two sections the resources starting doesn't run well, > but if you use the above constraints and the next resources section: > A group, as you use it, has implicit ordering AND co-location. So all your contraints are not nescessary. More questions: Why do you have "start" and "stop" operations? Throw them out. Why do you have resource_stickiness of "0" defined everywhere? Why don't you use default_resource_stickness of the crm_config section? Please check: What resources have to be started in what order? What resources have to be co-located and make groups based on the result of your considerations. Greetings, -- Dr. Michael Schwartzkopff MultiNET Services GmbH Addresse: Bretonischer Ring 7; 85630 Grasbrunn; Germany Tel: +49 - 89 - 45 69 11 0 Fax: +49 - 89 - 45 69 11 21 mob: +49 - 174 - 343 28 75 mail: [EMAIL PROTECTED] web: www.multinet.de Sitz der Gesellschaft: 85630 Grasbrunn Registergericht: Amtsgericht München HRB 114375 Geschäftsführer: Günter Jurgeneit, Hubert Martens --- PGP Fingerprint: F919 3919 FF12 ED5A 2801 DEA6 AA77 57A4 EDD8 979B Skype: misch42 _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
