Hi Andrew, Thank your for comment.
> Sorry, I'm not sure I understand the question. Sorry.... When we use resource_set in substitution for ordered of a thing of group resource, do we use "colocation set"? Or do we use "ordering set "? It does not seem to do work same as "group ordered=fase" if it is right to use "ordering set". Best Regards, Hideo Yamauchi. --- On Fri, 2013/3/22, Andrew Beekhof <and...@beekhof.net> wrote: > On Fri, Mar 22, 2013 at 12:34 PM, <renayama19661...@ybb.ne.jp> wrote: > > Hi Andrew, > > > > Thank your for comments. > > > >> > > 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> > >> > >> What are trying to achieve with this? It doesn't do anything because > >> there is nothing to collocate master or rep with. > >> The only value here is to show that rep would not be stopped when master > >> is. > > > > However, you made next reply. > > I used colocation_set in substitution for ordered=false. > > > >>>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). > > > > After all is it right that the substitute for ordered=false of group sets > > order_set? > > Sorry, I'm not sure I understand the question. > > > > > Best Regards, > > Hideo Yamauchi. > > > > > > > > --- On Fri, 2013/3/22, Andrew Beekhof <and...@beekhof.net> wrote: > > > >> > >> > >> On Thursday, March 7, 2013, 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> > >> > >> What are trying to achieve with this? It doesn't do anything because > >> there is nothing to collocate master or rep with. > >> The only value here is to show that rep would not be stopped when master > >> is. > >> (sip) > >> [root@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@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 > >> > >> > >> > >> You set target-role=stopped for master but rep did not stop? > >> If so that is certainly a bug. > >> > >> Best Regards, > >> 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 > _______________________________________________ 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