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

[renayama19661014 at ybb.ne.jp]

Hi Andrew,

I registered this question with Bugzilla.

 * http://bugs.clusterlabs.org/show_bug.cgi?id=5147

Best Regards,
Hideo Yamauchi.

--- On Thu, 2013/3/14, renayama19661014 at ybb.ne.jp <renayama19661014 at ybb.ne.jp> wrote:

> Hi Andrew,
> 
> > In "colocation", I used "resource_set".
> > However, a result did not include the change.
> 
> Please, about the result that I tried, give me comment.
> 
> Best Regards,
> Hideo Yamauchi.
> 
> --- On Thu, 2013/3/7, renayama19661014 at ybb.ne.jp <renayama19661014 at ybb.ne.jp> wrote:
> 
> > Hi Andrew,
> > 
> > > > You use the resource sets _instead_ of a group.
> > > > If you want group.ordered=false, then use a colocation set (with
> > > > sequential=true).
> > 
> > In "colocation", I used "resource_set".
> > However, a result did not include the change.
> > 
> > Will this result be a mistake of my setting?
> > 
> > Case 1) sequential=false
> > (snip)
> >     <constraints>
> >       <rsc_colocation id="test-colocation" score="INFINITY">
> >         <resource_set sequential="false" id="test-colocation-resource_set">
> >           <resource_ref id="vip-master"/>
> >           <resource_ref id="vip-rep"/>
> >         </resource_set>
> >       </rsc_colocation>
> >     </constraints>
> > (sip)
> > [root at rh63-heartbeat2 ~]# grep "Initiating action" /var/log/ha-log
> > Mar  8 00:20:52 rh63-heartbeat2 crmd: [22372]: info: te_rsc_command: Initiating action 2: probe_complete probe_complete on rh63-heartbeat1 - no waiting
> > Mar  8 00:20:52 rh63-heartbeat2 crmd: [22372]: info: te_rsc_command: Initiating action 3: probe_complete probe_complete on rh63-heartbeat2 (local) - no waiting
> > Mar  8 00:20:55 rh63-heartbeat2 crmd: [22372]: info: te_rsc_command: Initiating action 4: monitor vip-master_monitor_0 on rh63-heartbeat1
> > Mar  8 00:20:55 rh63-heartbeat2 crmd: [22372]: info: te_rsc_command: Initiating action 7: monitor vip-master_monitor_0 on rh63-heartbeat2 (local)
> > Mar  8 00:20:55 rh63-heartbeat2 crmd: [22372]: info: te_rsc_command: Initiating action 5: monitor vip-rep_monitor_0 on rh63-heartbeat1
> > Mar  8 00:20:55 rh63-heartbeat2 crmd: [22372]: info: te_rsc_command: Initiating action 8: monitor vip-rep_monitor_0 on rh63-heartbeat2 (local)
> > Mar  8 00:20:55 rh63-heartbeat2 crmd: [22372]: info: te_rsc_command: Initiating action 6: probe_complete probe_complete on rh63-heartbeat2 (local) - no waiting
> > Mar  8 00:20:56 rh63-heartbeat2 crmd: [22372]: info: te_rsc_command: Initiating action 3: probe_complete probe_complete on rh63-heartbeat1 - no waiting
> > Mar  8 00:20:56 rh63-heartbeat2 crmd: [22372]: info: te_rsc_command: Initiating action 5: start vip-master_start_0 on rh63-heartbeat1
> > Mar  8 00:20:58 rh63-heartbeat2 crmd: [22372]: info: te_rsc_command: Initiating action 1: stop vip-master_stop_0 on rh63-heartbeat1
> > 
> > 
> > Case 2) sequential=true
> > (snip)
> >     <constraints>
> >       <rsc_colocation id="test-colocation" score="INFINITY">
> >         <resource_set sequential="true" id="test-colocation-resource_set">
> >           <resource_ref id="vip-master"/>
> >           <resource_ref id="vip-rep"/>
> >         </resource_set>
> >       </rsc_colocation>
> >     </constraints>
> > (snip)
> > [root at rh63-heartbeat2 ~]# grep "Initiating action" /var/log/ha-log
> > Mar  7 23:54:44 rh63-heartbeat2 crmd: [22224]: info: te_rsc_command: Initiating action 2: probe_complete probe_complete on rh63-heartbeat1 - no waiting
> > Mar  7 23:54:44 rh63-heartbeat2 crmd: [22224]: info: te_rsc_command: Initiating action 3: probe_complete probe_complete on rh63-heartbeat2 (local) - no waiting
> > Mar  7 23:54:48 rh63-heartbeat2 crmd: [22224]: info: te_rsc_command: Initiating action 4: monitor vip-master_monitor_0 on rh63-heartbeat1
> > Mar  7 23:54:48 rh63-heartbeat2 crmd: [22224]: info: te_rsc_command: Initiating action 7: monitor vip-master_monitor_0 on rh63-heartbeat2 (local)
> > Mar  7 23:54:48 rh63-heartbeat2 crmd: [22224]: info: te_rsc_command: Initiating action 5: monitor vip-rep_monitor_0 on rh63-heartbeat1
> > Mar  7 23:54:48 rh63-heartbeat2 crmd: [22224]: info: te_rsc_command: Initiating action 8: monitor vip-rep_monitor_0 on rh63-heartbeat2 (local)
> > Mar  7 23:54:48 rh63-heartbeat2 crmd: [22224]: info: te_rsc_command: Initiating action 6: probe_complete probe_complete on rh63-heartbeat2 (local) - no waiting
> > Mar  7 23:54:49 rh63-heartbeat2 crmd: [22224]: info: te_rsc_command: Initiating action 3: probe_complete probe_complete on rh63-heartbeat1 - no waiting
> > Mar  7 23:54:49 rh63-heartbeat2 crmd: [22224]: info: te_rsc_command: Initiating action 5: start vip-master_start_0 on rh63-heartbeat1
> > Mar  7 23:54:51 rh63-heartbeat2 crmd: [22224]: info: te_rsc_command: Initiating action 1: stop vip-master_stop_0 on rh63-heartbeat1
> > 
> > 
> > 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
>