[Pacemaker] Problem : By colocations limitation, the resource appointment of the combination does not become effective.

[Andrew Beekhof]

On Mon, Apr 19, 2010 at 3:40 PM,  <renayama19661014 at ybb.ne.jp> wrote:
> Hi Andrew,
>
>> > Thank you for comment.
>> > But, does not the problem of the next email recur when I change it in INFINITY?
>> >
>> >  * http://www.gossamer-threads.com/lists/linuxha/pacemaker/60342
>>
>> No, as I previously explained:
>
> By an answer before you, pingd moves well.
> However, does setting of colocation of the resource that does not have an attribute go well when I
> change it in INFINITY?

Yes, because the -INFINITY + INFINITY = -INFINITY and therefore the
node wont be allowed to host the service.

> I think that initial placement does not go well.
>
> I confirm the movement that I set in INFINITY once again and report it.
>
> Best Regards,
> Hideo Yamauchi.
>
> --- Andrew Beekhof <andrew at beekhof.net> wrote:
>
>> 2010/4/19  <renayama19661014 at ybb.ne.jp>:
>> > Hi Andrew,
>> >
>> >> >> We want to realize start in order of the next.
>> >> >>  1) clnPingd, clnG3dummy1, clnG3dummy2, clnUMgroup01 (All resources start) -> UMgroup01
>> start
>> >> >>    * And the resource moves if a clone of one stops.
>> >> >>  2) clnPingd, clnG3dummy1, clnG3dummy2 (All resources start) -> OVDBgroup02-1 start
>> >> >>    * And the resource moves if a clone of one stops.
>> >>
>> >> If you want mandatory colocation, you need to use score=INFINITY
>> >
>> > Thank you for comment.
>> > But, does not the problem of the next email recur when I change it in INFINITY?
>> >
>> >  * http://www.gossamer-threads.com/lists/linuxha/pacemaker/60342
>>
>> No, as I previously explained:
>>
>> >> >> > > I was suggesting:
>> >> >> > >
>> >> >> > >  <rsc_colocation id="rsc_colocation01-3" rsc="UMgroup01"
>> >> >> > > with-rsc="clnUMgroup01" score="INFINITY"/>
>> >> >> > >
>> >> >> > > <rsc_location id="no-connectivity-01-1" rsc="UMgroup01">
>> >> >> > >    <rule id="clnPingd-exclude-rule" score="-INFINITY" boolean-op="or">
>> >> >> > >       <expression id="UMgroup01-clnPingd-exclude" attribute="clnPingd"
>> >> >> > > operation="not_defined"/>
>> >> >> > >       <expression id="UMgroup01-clnPingd-only-positive"
>> >> >> > > attribute="clnPingd" operation="lt" type="integer" value="1"/>
>> >> >> > >       <expression id="UMgroup01-clnPingd2-exclude"
>> >> >> > > attribute="clnPingd2" operation="not_defined"/>
>> >> >> > >       <expression id="UMgroup01-clnPingd2-only-positive"
>> >> >> > > attribute="clnPingd2" operation="lt" type="integer" value="1"/>
>> >> >> > >    </rule>
>> >> >> > > </rsc_location>
>> >> >> > >
>> >> >> > > <rsc_location id="no-connectivity-02-1" rsc="group02-1">
>> >> >> > >    <rule idref="clnPingd-exclude-rule"/>
>> >> >> > > </rsc_location>
>> >> >> > >
>> >> >> > > <rsc_location id="no-connectivity-02-1" rsc="group02-2">
>> >> >> > >    <rule idref="clnPingd-exclude-rule"/>
>> >> >> > > </rsc_location>
>>
>> _______________________________________________
>> 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
>>
>
>
> _______________________________________________
> 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
>