[Pacemaker] Problem : By colocations limitation, the resource appointment of the combination does not become effective.
Andrew Beekhof
andrew at beekhof.net
Mon Mar 8 09:59:38 UTC 2010
2010/3/5 <renayama19661014 at ybb.ne.jp>:
> Hi All,
>
> We test complicated colocation appointment.
>
> We did resource appointment to start by limitation of colocation together.
>
> But, the resource that set limitation starts when the resource that we appointed does not start in a
> certain procedure.
>
> We did the following appointment.
>
> <rsc_colocation id="rsc_colocation01-1" rsc="UMgroup01" with-rsc="clnPingd" score="1000"/>
>
> When clnPingd did not start, we met with the phenomenon that UMgroup01 started.
This is normal for constraints with scores < INFINITY.
Anything < INFINITY is "preferable but not mandatory"
More information about the Pacemaker
mailing list