<HTML><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.19190"></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>Thank you for pointing me at this discussion thread. The configuration did help me to achieve what I was looking for. Now though I wonder if I should because of the threads end-point comment.</DIV>
<DIV> </DIV>
<DIV>Any idea what the background explanation may be for the comment:</DIV>
<DIV>"an unordered and/or uncolocated groups are an abomination"</DIV>
<DIV> </DIV>
<DIV>The thread stops with:</DIV>
<DIV>-------------------------</DIV>
<DIV>Unordered and/or uncolocated groups are an abomination.<BR>Is that enough light?<BR>-------------------------</DIV>
<DIV><BR>Nick<BR><BR>>>> Florian Crouzat <gentoo@floriancrouzat.net> 2012-06-14 09:56 >>><BR>Le 14/06/2012 14:55, Nicolaas Stuyt a écrit :<BR>> Hello,<BR>> Is there a way to affect a groups ordering behavior? The default appears<BR>> to be left to right which I can understand. However if I wish to create<BR>> a group of "like primitives" and not primitives who are dependant on<BR>> each other - for example a list of (ocf::heartbeat:Filesystem)<BR>> primitives - then I care less about the order. I was hoping to specify a<BR>> meta characteristic like "lazy" I guess; something like meta<BR>> order="lazy" or "not-applicable". This ordering behavior seems to exist<BR>> in colocation as well.<BR>> What I wish to achieve is to take a file system resource down - say for<BR>> maintenance and then allow it to come back when maintenance is completed<BR>> without affecting the other Filesystem primitives down the list.<BR>> To provide a visual illustration of this I created a cloned group of<BR>> dummies using (ocf::pacemaker:Dummy) and I have stopped just the last<BR>> dummy primitive:<BR>> Clone Set: cl_dummies [grp_dummies]<BR>> Resource Group: grp_dummies:0<BR>> dummy1:0 (ocf::pacemaker:Dummy): Started node1<BR>> dummy2:0 (ocf::pacemaker:Dummy): Started node1<BR>> dummy3:0 (ocf::pacemaker:Dummy): Started node1<BR>> dummy4:0 (ocf::pacemaker:Dummy): Started node1<BR>> dummy5:0 (ocf::pacemaker:Dummy): Stopped<BR>> Resource Group: grp_dummies:1<BR>> dummy1:1 (ocf::pacemaker:Dummy): Started node2<BR>> dummy2:1 (ocf::pacemaker:Dummy): Started node2<BR>> dummy3:1 (ocf::pacemaker:Dummy): Started node2<BR>> dummy4:1 (ocf::pacemaker:Dummy): Started node2<BR>> dummy5:1 (ocf::pacemaker:Dummy): Stopped<BR>> When all are running crm_mon presents as:<BR>> Clone Set: cl_dummies [grp_dummies]<BR>> Started: [ node1 node2]<BR>> What I want to achieve is to take a middle dummy primitive out but leave<BR>> the rest running. When I do that - for example on dummy3; dummies 4 and<BR>> 5 also get taken out such that I am left with this:<BR>> Clone Set: cl_dummies [grp_dummies]<BR>> Resource Group: grp_dummies:0<BR>> dummy1:0 (ocf::pacemaker:Dummy): Started node1<BR>> dummy2:0 (ocf::pacemaker:Dummy): Started node1<BR>> dummy3:0 (ocf::pacemaker:Dummy): Stopped<BR>> dummy4:0 (ocf::pacemaker:Dummy): Stopped<BR>> dummy5:0 (ocf::pacemaker:Dummy): Stopped<BR>> Resource Group: grp_dummies:1<BR>> dummy1:1 (ocf::pacemaker:Dummy): Started node2<BR>> dummy2:1 (ocf::pacemaker:Dummy): Started node2<BR>> dummy3:1 (ocf::pacemaker:Dummy): Stopped<BR>> dummy4:1 (ocf::pacemaker:Dummy): Stopped<BR>> dummy5:1 (ocf::pacemaker:Dummy): Stopped<BR>> What I would like is this:<BR>> Clone Set: cl_dummies [grp_dummies]<BR>> Resource Group: grp_dummies:0<BR>> dummy1:0 (ocf::pacemaker:Dummy): Started node1<BR>> dummy2:0 (ocf::pacemaker:Dummy): Started node1<BR>> dummy3:0 (ocf::pacemaker:Dummy): Stopped<BR>> dummy4:0 (ocf::pacemaker:Dummy): Started node1<BR>> dummy5:0 (ocf::pacemaker:Dummy): Started node1<BR>> Resource Group: grp_dummies:1<BR>> dummy1:1 (ocf::pacemaker:Dummy): Started node2<BR>> dummy2:1 (ocf::pacemaker:Dummy): Started node2<BR>> dummy3:1 (ocf::pacemaker:Dummy): Stopped<BR>> dummy4:1 (ocf::pacemaker:Dummy): Started node2<BR>> dummy5:1 (ocf::pacemaker:Dummy): Started node2<BR>> A work around I have considered is to edit the group and resort the list<BR>> so that the Filesystem primitive I'm interested in working on is named<BR>> last but I wonder if I'll remember ;-) to do that the next time I need<BR>> to perform maintenance.<BR>> Or is there a better way to do this that I have not been introduced too yet?<BR>> Regards,<BR>> Nick<BR><BR>It's already been discussed a couple times.<BR>See <BR><A href="http://oss.clusterlabs.org/pipermail/pacemaker/2011-March/009435.html">http://oss.clusterlabs.org/pipermail/pacemaker/2011-March/009435.html</A> <BR>and follow link/answers.<BR><BR>-- <BR>Cheers,<BR>Florian Crouzat<BR><BR>_______________________________________________<BR>Pacemaker mailing list: Pacemaker@oss.clusterlabs.org<BR><A href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</A><BR><BR>Project Home: <A href="http://www.clusterlabs.org">http://www.clusterlabs.org</A><BR>Getting started: <A href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</A><BR>Bugs: <A href="http://bugs.clusterlabs.org">http://bugs.clusterlabs.org</A><BR></DIV></BODY></HTML>