Hi Andrew, Thank you for comments.
> > Using ordering_set and colocation_set, is it impossible to perform movement > > same as "ordered=false" of the group resource? > > Yes, because they're not the same thing. > > Setting "sequential=false" is not at all like setting "ordered=false". > Setting "ordered=false" is the equivalent of _removing_ <rsc_order > id="test-order"> completely. Which next case does your answer correspond to? Case 1) Cannot replace "ordered=false" of group with "sequential". Therefore, the "ordered" attribute of the group resource continues being supported from now on. Case 2) It works in the same way if I exclude rsc_order id="test-order" like the next setting. (rsc_colocation sequential="false", remove rsc_order id="test-order".) (snip) <resources> <group id="testGroup01"> <primitive class="ocf" type="Dummy" provider="heartbeat" id="vip-master"> <operations> (snip) <primitive class="ocf" type="Dummy" provider="heartbeat" id="vip-rep"> <operations> </group> (snip) <constraints> <rsc_colocation id="test-colocation"> <resource_set sequential="false" id="test-colocation-resource_set"> <resource_ref id="vip-master"/> <resource_ref id="vip-rep"/> </resource_set> </rsc_colocation> </constraints> (snip) Case 3) There is a method to set ordered="false" of group elsewhere. Best Regards, Hideo Yamauchi. --- On Mon, 2013/4/8, Andrew Beekhof <and...@beekhof.net> wrote: > > On 22/03/2013, at 3:17 PM, renayama19661...@ybb.ne.jp wrote: > > > Hi Andrew, > > > > Thank you for comments. > > > > We demand time and the same movement that appointed ordered=false of the > > group resource. > > > > * Case 0 - group : orderded=false > > * At the time of orderded=false, it takes start of vip-rep. ------------> > >We demand!! > > {{{ > > (snip) > > <resources> > > <group id="testGroup01"> > > <meta_attributes id="master-group-meta_attributes"> > > <nvpair id="master-group-meta_attributes-ordered" name="ordered" > >value="false"/> > > </meta_attributes> > > <primitive class="ocf" type="Dummy1" provider="heartbeat" > >id="vip-master"> > > <operations> > > <op id="op-Dummy01-start" interval="0" name="start" > >timeout="60s" on-fail="restart"/> > > <op id="op-Dummy01-monitor" interval="10" name="monitor" > >timeout="60s" on-fail="restart"/> > > <op id="op-Dummy01-stop" interval="0" name="stop" timeout="60s" > >on-fail="block"/> > > </operations> > > </primitive> > > <primitive class="ocf" type="Dummy2" provider="heartbeat" > >id="vip-rep"> > > <operations> > > <op id="op-Dummy02-start" interval="0" name="start" > >timeout="60s" on-fail="restart"/> > > <op id="op-Dummy02-monitor" interval="10" name="monitor" > >timeout="60s" on-fail="restart"/> > > <op id="op-Dummy02-stop" interval="0" name="stop" timeout="60s" > >on-fail="block"/> > > </operations> > > </primitive> > > </group> > > </resources> > > (snip) > > [root@rh64-heartbeat1 ~]# grep "Initiating action" /var/log/ha-log > > Mar 22 21:45:01 rh64-heartbeat1 crmd: [2625]: info: te_rsc_command: > > Initiating action 2: probe_complete probe_complete on rh64-heartbeat1 > > (local) - no waiting > > Mar 22 21:46:36 rh64-heartbeat1 crmd: [2625]: info: te_rsc_command: > > Initiating action 4: monitor vip-master_monitor_0 on rh64-heartbeat1 (local) > > Mar 22 21:46:36 rh64-heartbeat1 crmd: [2625]: info: te_rsc_command: > > Initiating action 5: monitor vip-rep_monitor_0 on rh64-heartbeat1 (local) > > Mar 22 21:46:36 rh64-heartbeat1 crmd: [2625]: info: te_rsc_command: > > Initiating action 3: probe_complete probe_complete on rh64-heartbeat1 > > (local) - no waiting > > Mar 22 21:46:36 rh64-heartbeat1 crmd: [2625]: info: te_rsc_command: > > Initiating action 6: start vip-master_start_0 on rh64-heartbeat1 (local) > > Mar 22 21:46:36 rh64-heartbeat1 crmd: [2625]: info: te_rsc_command: > > Initiating action 8: start vip-rep_start_0 on rh64-heartbeat1 (local) > > Mar 22 21:46:37 rh64-heartbeat1 crmd: [2625]: info: te_rsc_command: > > Initiating action 1: stop vip-master_stop_0 on rh64-heartbeat1 (local) > > Mar 22 21:46:37 rh64-heartbeat1 crmd: [2625]: info: te_rsc_command: > > Initiating action 5: stop vip-rep_stop_0 on rh64-heartbeat1 (local) > > }}} > > > > > > I tried an all combination of ordering_set and colocation_set. > > However, start of vip-rep was not carried out by all combinations. > > * I do not do the "ordered=false" designation of the group resource. > > > > * Case 1 : true/true > > {{{ > > (snip) > > <resources> > > <group id="testGroup01"> > > <primitive class="ocf" type="Dummy1" provider="heartbeat" > >id="vip-master"> > > <operations> > > (snip) > > <constraints> > > <rsc_colocation id="test-colocation"> > > <resource_set sequential="true" > >id="test-colocation-resource_set"> > > <resource_ref id="vip-master"/> > > <resource_ref id="vip-rep"/> > > </resource_set> > > </rsc_colocation> > > <rsc_order id="test-order"> > > <resource_set sequential="true" id="test-order-resource_set"> > > <resource_ref id="vip-master"/> > > <resource_ref id="vip-rep"/> > > </resource_set> > > </rsc_order> > > </constraints> > > > > > > [root@rh64-heartbeat1 ~]# grep "Initiating action" /var/log/ha-log > > Mar 22 21:30:26 rh64-heartbeat1 crmd: [2076]: info: te_rsc_command: > > Initiating action 2: probe_complete probe_complete on rh64-heartbeat1 > > (local) - no waiting > > Mar 22 21:33:36 rh64-heartbeat1 crmd: [2076]: info: te_rsc_command: > > Initiating action 8: monitor vip-master_monitor_0 on rh64-heartbeat1 (local) > > Mar 22 21:33:36 rh64-heartbeat1 crmd: [2076]: info: te_rsc_command: > > Initiating action 9: monitor vip-rep_monitor_0 on rh64-heartbeat1 (local) > > Mar 22 21:33:36 rh64-heartbeat1 crmd: [2076]: info: te_rsc_command: > > Initiating action 7: probe_complete probe_complete on rh64-heartbeat1 > > (local) - no waiting > > Mar 22 21:33:36 rh64-heartbeat1 crmd: [2076]: info: te_rsc_command: > > Initiating action 10: start vip-master_start_0 on rh64-heartbeat1 (local) > > Mar 22 21:33:36 rh64-heartbeat1 crmd: [2076]: info: te_rsc_command: > > Initiating action 1: stop vip-master_stop_0 on rh64-heartbeat1 (local) > > }}} > > * Case 2 : true/false > > {{{ > > (snip) > > <resources> > > <group id="testGroup01"> > > <primitive class="ocf" type="Dummy1" provider="heartbeat" > >id="vip-master"> > > <operations> > > (snip) > > <constraints> > > <rsc_colocation id="test-colocation"> > > <resource_set sequential="true" > >id="test-colocation-resource_set"> > > <resource_ref id="vip-master"/> > > <resource_ref id="vip-rep"/> > > </resource_set> > > </rsc_colocation> > > <rsc_order id="test-order"> > > <resource_set sequential="false" > >id="test-order-resource_set"> > > <resource_ref id="vip-master"/> > > <resource_ref id="vip-rep"/> > > </resource_set> > > </rsc_order> > > </constraints> > > > > > > [root@rh64-heartbeat1 ~]# grep "Initiating action" /var/log/ha-log > > Mar 22 21:36:38 rh64-heartbeat1 crmd: [2222]: info: te_rsc_command: > > Initiating action 2: probe_complete probe_complete on rh64-heartbeat1 > > (local) - no waiting > > Mar 22 21:36:49 rh64-heartbeat1 crmd: [2222]: info: te_rsc_command: > > Initiating action 8: monitor vip-master_monitor_0 on rh64-heartbeat1 (local) > > Mar 22 21:36:49 rh64-heartbeat1 crmd: [2222]: info: te_rsc_command: > > Initiating action 9: monitor vip-rep_monitor_0 on rh64-heartbeat1 (local) > > Mar 22 21:36:49 rh64-heartbeat1 crmd: [2222]: info: te_rsc_command: > > Initiating action 7: probe_complete probe_complete on rh64-heartbeat1 > > (local) - no waiting > > Mar 22 21:36:49 rh64-heartbeat1 crmd: [2222]: info: te_rsc_command: > > Initiating action 10: start vip-master_start_0 on rh64-heartbeat1 (local) > > Mar 22 21:36:50 rh64-heartbeat1 crmd: [2222]: info: te_rsc_command: > > Initiating action 1: stop vip-master_stop_0 on rh64-heartbeat1 (local) > > > > }}} > > * Cse 3 : false/true > > {{{ > > (snip) > > <resources> > > <group id="testGroup01"> > > <primitive class="ocf" type="Dummy1" provider="heartbeat" > >id="vip-master"> > > <operations> > > (snip) > > <constraints> > > <rsc_colocation id="test-colocation"> > > <resource_set sequential="false" > >id="test-colocation-resource_set"> > > <resource_ref id="vip-master"/> > > <resource_ref id="vip-rep"/> > > </resource_set> > > </rsc_colocation> > > <rsc_order id="test-order"> > > <resource_set sequential="true" id="test-order-resource_set"> > > <resource_ref id="vip-master"/> > > <resource_ref id="vip-rep"/> > > </resource_set> > > </rsc_order> > > </constraints> > > > > [root@rh64-heartbeat1 ~]# grep "Initiating action" /var/log/ha-log > > Mar 22 21:38:51 rh64-heartbeat1 crmd: [2358]: info: te_rsc_command: > > Initiating action 2: probe_complete probe_complete on rh64-heartbeat1 > > (local) - no waiting > > Mar 22 21:39:07 rh64-heartbeat1 crmd: [2358]: info: te_rsc_command: > > Initiating action 8: monitor vip-master_monitor_0 on rh64-heartbeat1 (local) > > Mar 22 21:39:07 rh64-heartbeat1 crmd: [2358]: info: te_rsc_command: > > Initiating action 9: monitor vip-rep_monitor_0 on rh64-heartbeat1 (local) > > Mar 22 21:39:07 rh64-heartbeat1 crmd: [2358]: info: te_rsc_command: > > Initiating action 7: probe_complete probe_complete on rh64-heartbeat1 > > (local) - no waiting > > Mar 22 21:39:07 rh64-heartbeat1 crmd: [2358]: info: te_rsc_command: > > Initiating action 10: start vip-master_start_0 on rh64-heartbeat1 (local) > > Mar 22 21:39:07 rh64-heartbeat1 crmd: [2358]: info: te_rsc_command: > > Initiating action 1: stop vip-master_stop_0 on rh64-heartbeat1 (local) > > > > }}} > > * Case 4 : false/false > > {{{ > > (snip) > > <resources> > > <group id="testGroup01"> > > <primitive class="ocf" type="Dummy1" provider="heartbeat" > >id="vip-master"> > > <operations> > > (snip) > > <constraints> > > <rsc_colocation id="test-colocation"> > > <resource_set sequential="false" > >id="test-colocation-resource_set"> > > <resource_ref id="vip-master"/> > > <resource_ref id="vip-rep"/> > > </resource_set> > > </rsc_colocation> > > <rsc_order id="test-order"> > > <resource_set sequential="false" > >id="test-order-resource_set"> > > <resource_ref id="vip-master"/> > > <resource_ref id="vip-rep"/> > ></resource_set> > > </rsc_order> > > </constraints> > > > > [root@rh64-heartbeat1 ~]# grep "Initiating action" /var/log/ha-log > > Mar 22 21:41:11 rh64-heartbeat1 crmd: [2491]: info: te_rsc_command: > > Initiating action 2: probe_complete probe_complete on rh64-heartbeat1 > > (local) - no waiting > > Mar 22 21:42:16 rh64-heartbeat1 crmd: [2491]: info: te_rsc_command: > > Initiating action 8: monitor vip-master_monitor_0 on rh64-heartbeat1 (local) > > Mar 22 21:42:16 rh64-heartbeat1 crmd: [2491]: info: te_rsc_command: > > Initiating action 9: monitor vip-rep_monitor_0 on rh64-heartbeat1 (local) > > Mar 22 21:42:16 rh64-heartbeat1 crmd: [2491]: info: te_rsc_command: > > Initiating action 7: probe_complete probe_complete on rh64-heartbeat1 > > (local) - no waiting > > Mar 22 21:42:16 rh64-heartbeat1 crmd: [2491]: info: te_rsc_command: > > Initiating action 10: start vip-master_start_0 on rh64-heartbeat1 (local) > > Mar 22 21:42:16 rh64-heartbeat1 crmd: [2491]: info: te_rsc_command: > > Initiating action 1: stop vip-master_stop_0 on rh64-heartbeat1 (local) > > > > }}} > > > > Using ordering_set and colocation_set, is it impossible to perform movement > > same as "ordered=false" of the group resource? > > Yes, because they're not the same thing. > > Setting "sequential=false" is not at all like setting "ordered=false". > Setting "ordered=false" is the equivalent of _removing_ <rsc_order > id="test-order"> completely. > > > > > Best Reagards, > > Hideo Yamauchi. > > > > > > > > _______________________________________________ > > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > > > Project Home: http://www.clusterlabs.org > > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > > Bugs: http://bugs.clusterlabs.org > > _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org