<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>Hello,</DIV>
<DIV> </DIV>
<DIV>Is there a way to affect a groups ordering behavior? The default appears to be left to right which I can understand. However if I wish to create a group of "like primitives" and not primitives who are dependant on each other - for example a list of (ocf::heartbeat:Filesystem) primitives - then I care less about the order. I was hoping to specify a meta characteristic like "lazy" I guess; something like meta order="lazy" or "not-applicable". This ordering behavior seems to exist in colocation as well.</DIV>
<DIV> </DIV>
<DIV>What I wish to achieve is to take a file system resource down - say for maintenance and then allow it to come back when maintenance is completed without affecting the other Filesystem primitives down the list.</DIV>
<DIV> </DIV>
<DIV>To provide a visual illustration of this I created a cloned group of dummies using (ocf::pacemaker:Dummy) and I have stopped just the last dummy primitive:</DIV>
<DIV> </DIV>
<DIV> 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</DIV>
<DIV> </DIV>
<DIV>When all are running crm_mon presents as:</DIV>
<DIV> </DIV>
<DIV> Clone Set: cl_dummies [grp_dummies]<BR> Started: [ node1 node2]<BR></DIV>
<DIV>What I want to achieve is to take a middle dummy primitive out but leave the rest running. When I do that - for example on dummy3; dummies 4 and 5 also get taken out such that I am left with this:</DIV>
<DIV> </DIV>
<DIV> 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</DIV>
<DIV> </DIV>
<DIV>What I would like is this:</DIV>
<DIV> </DIV>
<DIV> 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</DIV>
<DIV> </DIV>
<DIV>A work around I have considered is to edit the group and resort the list so that the Filesystem primitive I'm interested in working on is named last but I wonder if I'll remember ;-) to do that the next time I need to perform maintenance.</DIV>
<DIV> </DIV>
<DIV>Or is there a better way to do this that I have not been introduced too yet?</DIV>
<DIV> </DIV>
<DIV>Regards,</DIV>
<DIV>Nick</DIV></BODY></HTML>