[Pacemaker] [Question]About "sequential" designation of resource_set.

[renayama19661014 at ybb.ne.jp]

Hi Andrew,

Thank you for comment.

It was colocation.
I make modifications and confirm movement.

Many Thanks!
Hideo Yamauchi.

--- On Thu, 2013/3/7, Andrew Beekhof <andrew at beekhof.net> wrote:

> Ohhhhh!
> 
> You use the resource sets _instead_ of a group.
> If you want group.ordered=false, then use a colocation set (with
> sequential=true).
> If you want group.colocated=false, then use an ordering set (with
> sequential=true).
> 
> Hope that helps :)
> 
> On Thu, Mar 7, 2013 at 3:16 PM,  <renayama19661014 at ybb.ne.jp> wrote:
> > Hi Andrew,
> >
> > Thank you for comments.
> >
> >> > Case 3) group resource_set sequential=false
> >> >  * Start of vip-rep waits for start of vip-master and is published.
> >> >  * I expected a result same as the first case.
> >>
> >> Me too. Have you got the relevant PE file?
> >
> > I attached the thing which just collected hb_report.
> >
> > Best Regards,
> > Hideo Yamauchi.
> >
> >
> >
> > --- On Thu, 2013/3/7, Andrew Beekhof <andrew at beekhof.net> wrote:
> >
> >> On Thu, Mar 7, 2013 at 1:27 PM,  <renayama19661014 at ybb.ne.jp> wrote:
> >> > Hi Andrew,
> >> >
> >> > I tried "resource_set .... sequential" designation.
> >> >  *  http://www.gossamer-threads.com/lists/linuxha/pacemaker/84578
> >> >
> >> > I caused an error in start of the vip-master resource and confirmed movement.
> >> >
> >> > (snip)
> >> >       <group id="master-group">
> >> >         <primitive class="ocf" id="vip-master" provider="pacemaker" type="Dummy2">
> >> >           <operations>
> >> >             <op id="vip-master-start-0s" interval="0s" name="start" on-fail="restart" timeout="60s"/>
> >> >             <op id="vip-master-monitor-10s" interval="10s" name="monitor" on-fail="restart" timeout="60s"/>
> >> >             <op id="vip-master-stop-0s" interval="0s" name="stop" on-fail="block" timeout="60s"/>
> >> >           </operations>
> >> >         </primitive>
> >> >         <primitive class="ocf" id="vip-rep" provider="pacemaker" type="Dummy">
> >> >           <operations>
> >> >             <op id="vip-rep-start-0s" interval="0s" name="start" on-fail="stop" timeout="60s"/>
> >> >             <op id="vip-rep-monitor-10s" interval="10s" name="monitor" on-fail="restart" timeout="60s"/>
> >> >             <op id="vip-rep-stop-0s" interval="0s" name="stop" on-fail="block" timeout="60s"/>
> >> >           </operations>
> >> >         </primitive>
> >> >       </group>
> >> > (snip)
> >> >
> >> > By the ordered designation of the group resource, the difference that I expected appeared.( Case 1 and Case 2)
> >> > However, by the "sequential" designation, the difference that I expected did not appear.(Case 3 and Case 4)
> >> >
> >> > (snip)
> >> >     <constraints>
> >> >         <rsc_order id="test-order">
> >> >                 <resource_set sequential="true" id="test-order-resource_set">  ---> or "false"
> >> >                         <resource_ref id="vip-master"/>
> >> >                         <resource_ref id="vip-rep"/>
> >> >                 </resource_set>
> >> >         </rsc_order>
> >> >     </constraints>
> >> > (snip)
> >> >
> >> >
> >> > Case 1) group meta_attribute ordered=false
> >> >  * Start of vip-rep is published without waiting for start of vip-master.
> >> >
> >> > [root at rh63-heartbeat2 ~]# grep "Initiating action" /var/log/ha-log
> >> > Mar  7 19:40:50 rh63-heartbeat2 crmd: [18992]: info: te_rsc_command: Initiating action 2: probe_complete probe_complete on rh63-heartbeat1 - no waiting
> >> > Mar  7 19:40:50 rh63-heartbeat2 crmd: [18992]: info: te_rsc_command: Initiating action 3: probe_complete probe_complete on rh63-heartbeat2 (local) - no waiting
> >> > Mar  7 19:41:24 rh63-heartbeat2 crmd: [18992]: info: te_rsc_command: Initiating action 4: monitor vip-master_monitor_0 on rh63-heartbeat1
> >> > Mar  7 19:41:24 rh63-heartbeat2 crmd: [18992]: info: te_rsc_command: Initiating action 7: monitor vip-master_monitor_0 on rh63-heartbeat2 (local)
> >> > Mar  7 19:41:24 rh63-heartbeat2 crmd: [18992]: info: te_rsc_command: Initiating action 5: monitor vip-rep_monitor_0 on rh63-heartbeat1
> >> > Mar  7 19:41:24 rh63-heartbeat2 crmd: [18992]: info: te_rsc_command: Initiating action 8: monitor vip-rep_monitor_0 on rh63-heartbeat2 (local)
> >> > Mar  7 19:41:24 rh63-heartbeat2 crmd: [18992]: info: te_rsc_command: Initiating action 6: probe_complete probe_complete on rh63-heartbeat2 (local) - no waiting
> >> > Mar  7 19:41:25 rh63-heartbeat2 crmd: [18992]: info: te_rsc_command: Initiating action 3: probe_complete probe_complete on rh63-heartbeat1 - no waiting
> >> > Mar  7 19:41:25 rh63-heartbeat2 crmd: [18992]: info: te_rsc_command: Initiating action 5: start vip-master_start_0 on rh63-heartbeat1
> >> > Mar  7 19:41:25 rh63-heartbeat2 crmd: [18992]: info: te_rsc_command: Initiating action 7: start vip-rep_start_0 on rh63-heartbeat1
> >> > Mar  7 19:41:26 rh63-heartbeat2 crmd: [18992]: info: te_rsc_command: Initiating action 8: monitor vip-rep_monitor_10000 on rh63-heartbeat1
> >> > Mar  7 19:41:27 rh63-heartbeat2 crmd: [18992]: info: te_rsc_command: Initiating action 2: stop vip-master_stop_0 on rh63-heartbeat1
> >> > Mar  7 19:41:28 rh63-heartbeat2 crmd: [18992]: info: te_rsc_command: Initiating action 6: stop vip-rep_stop_0 on rh63-heartbeat1
> >> >
> >> >
> >> > Case 2) group meta_attribute ordered=true
> >> >  * Start of vip-rep waits for start of vip-master and is published.
> >> >
> >> > [root at rh63-heartbeat2 ~]# grep "Initiating action" /var/log/ha-log
> >> > Mar  7 19:34:37 rh63-heartbeat2 crmd: [18865]: info: te_rsc_command: Initiating action 2: probe_complete probe_complete on rh63-heartbeat1 - no waiting
> >> > Mar  7 19:34:37 rh63-heartbeat2 crmd: [18865]: info: te_rsc_command: Initiating action 3: probe_complete probe_complete on rh63-heartbeat2 (local) - no waiting
> >> > Mar  7 19:35:42 rh63-heartbeat2 crmd: [18865]: info: te_rsc_command: Initiating action 4: monitor vip-master_monitor_0 on rh63-heartbeat1
> >> > Mar  7 19:35:42 rh63-heartbeat2 crmd: [18865]: info: te_rsc_command: Initiating action 7: monitor vip-master_monitor_0 on rh63-heartbeat2 (local)
> >> > Mar  7 19:35:42 rh63-heartbeat2 crmd: [18865]: info: te_rsc_command: Initiating action 5: monitor vip-rep_monitor_0 on rh63-heartbeat1
> >> > Mar  7 19:35:42 rh63-heartbeat2 crmd: [18865]: info: te_rsc_command: Initiating action 8: monitor vip-rep_monitor_0 on rh63-heartbeat2 (local)
> >> > Mar  7 19:35:42 rh63-heartbeat2 crmd: [18865]: info: te_rsc_command: Initiating action 6: probe_complete probe_complete on rh63-heartbeat2 (local) - no waiting
> >> > Mar  7 19:35:43 rh63-heartbeat2 crmd: [18865]: info: te_rsc_command: Initiating action 3: probe_complete probe_complete on rh63-heartbeat1 - no waiting
> >> > Mar  7 19:35:43 rh63-heartbeat2 crmd: [18865]: info: te_rsc_command: Initiating action 5: start vip-master_start_0 on rh63-heartbeat1
> >> > Mar  7 19:35:45 rh63-heartbeat2 crmd: [18865]: info: te_rsc_command: Initiating action 1: stop vip-master_stop_0 on rh63-heartbeat1
> >> >
> >> >
> >> > Case 3) group resource_set sequential=false
> >> >  * Start of vip-rep waits for start of vip-master and is published.
> >> >  * I expected a result same as the first case.
> >>
> >> Me too. Have you got the relevant PE file?
> >>
> >> >
> >> > [root at rh63-heartbeat2 ~]# grep "Initiating action" /var/log/ha-log
> >> > Mar  7 19:43:50 rh63-heartbeat2 crmd: [19113]: info: te_rsc_command: Initiating action 2: probe_complete probe_complete on rh63-heartbeat1 - no waiting
> >> > Mar  7 19:43:50 rh63-heartbeat2 crmd: [19113]: info: te_rsc_command: Initiating action 3: probe_complete probe_complete on rh63-heartbeat2 (local) - no waiting
> >> > Mar  7 19:44:03 rh63-heartbeat2 crmd: [19113]: info: te_rsc_command: Initiating action 8: monitor vip-master_monitor_0 on rh63-heartbeat1
> >> > Mar  7 19:44:03 rh63-heartbeat2 crmd: [19113]: info: te_rsc_command: Initiating action 11: monitor vip-master_monitor_0 on rh63-heartbeat2 (local)
> >> > Mar  7 19:44:03 rh63-heartbeat2 crmd: [19113]: info: te_rsc_command: Initiating action 9: monitor vip-rep_monitor_0 on rh63-heartbeat1
> >> > Mar  7 19:44:03 rh63-heartbeat2 crmd: [19113]: info: te_rsc_command: Initiating action 12: monitor vip-rep_monitor_0 on rh63-heartbeat2 (local)
> >> > Mar  7 19:44:04 rh63-heartbeat2 crmd: [19113]: info: te_rsc_command: Initiating action 10: probe_complete probe_complete on rh63-heartbeat2 (local) - no waiting
> >> > Mar  7 19:44:05 rh63-heartbeat2 crmd: [19113]: info: te_rsc_command: Initiating action 7: probe_complete probe_complete on rh63-heartbeat1 - no waiting
> >> > Mar  7 19:44:05 rh63-heartbeat2 crmd: [19113]: info: te_rsc_command: Initiating action 9: start vip-master_start_0 on rh63-heartbeat1
> >> > Mar  7 19:44:07 rh63-heartbeat2 crmd: [19113]: info: te_rsc_command: Initiating action 1: stop vip-master_stop_0 on rh63-heartbeat1
> >> >
> >> >
> >> > Case 4) group resource_set sequential=true
> >> >  * Start of vip-rep waits for start of vip-master and is published.
> >> >
> >> > [root at rh63-heartbeat2 ~]# grep "Initiating action" /var/log/ha-log
> >> > Mar  7 19:48:25 rh63-heartbeat2 crmd: [19239]: info: te_rsc_command: Initiating action 2: probe_complete probe_complete on rh63-heartbeat1 - no waiting
> >> > Mar  7 19:48:25 rh63-heartbeat2 crmd: [19239]: info: te_rsc_command: Initiating action 3: probe_complete probe_complete on rh63-heartbeat2 (local) - no waiting
> >> > Mar  7 19:48:30 rh63-heartbeat2 crmd: [19239]: info: te_rsc_command: Initiating action 8: monitor vip-master_monitor_0 on rh63-heartbeat1
> >> > Mar  7 19:48:30 rh63-heartbeat2 crmd: [19239]: info: te_rsc_command: Initiating action 11: monitor vip-master_monitor_0 on rh63-heartbeat2 (local)
> >> > Mar  7 19:48:30 rh63-heartbeat2 crmd: [19239]: info: te_rsc_command: Initiating action 9: monitor vip-rep_monitor_0 on rh63-heartbeat1
> >> > Mar  7 19:48:30 rh63-heartbeat2 crmd: [19239]: info: te_rsc_command: Initiating action 12: monitor vip-rep_monitor_0 on rh63-heartbeat2 (local)
> >> > Mar  7 19:48:30 rh63-heartbeat2 crmd: [19239]: info: te_rsc_command: Initiating action 10: probe_complete probe_complete on rh63-heartbeat2 (local) - no waiting
> >> > Mar  7 19:48:31 rh63-heartbeat2 crmd: [19239]: info: te_rsc_command: Initiating action 7: probe_complete probe_complete on rh63-heartbeat1 - no waiting
> >> > Mar  7 19:48:31 rh63-heartbeat2 crmd: [19239]: info: te_rsc_command: Initiating action 9: start vip-master_start_0 on rh63-heartbeat1
> >> > Mar  7 19:48:33 rh63-heartbeat2 crmd: [19239]: info: te_rsc_command: Initiating action 1: stop vip-master_stop_0 on rh63-heartbeat1
> >> >
> >> >
> >> > Does designation of my "resource_set" have a problem?
> >> > Or does not "resource_set" move well in Pacemaker1.0.13?
> >> >
> >> > Best Regards,
> >> > Hideo Yamauchi.
> >> >
> >> >
> >> > _______________________________________________
> >> > Pacemaker mailing list: Pacemaker at 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 at 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
> >
>