[Pacemaker] colocation that doesn't

Dejan Muhamedagic dejanmm at fastmail.fm
Thu Nov 4 05:37:15 EDT 2010


On Wed, Nov 03, 2010 at 04:24:07PM -0700, Alan Jones wrote:
> I running with Pacemaker and Corosync 1.2.7.
> I have a simple config below where colocation seems to have the opposite effect.
> Note that if you force myprim's location then mystateful's Master will
> colocate correctly.
> The command I use to force is: location myprim-loc myprim -inf:
> node-not-to-run-myprim
> My understanding is that the colocation rule for mystateful should
> apply to the location of myprim regardless of what rules placed myprim
> on that node.
> Is this a known bug in
> Alan
> primitive myprim ocf:pacemaker:Dummy
> primitive mystateful ocf:pacemaker:Stateful
> ms mystateful-ms mystateful meta master-max="1" master-node-max="1" \
>     clone-max="2" clone-node-max="1" notify="true"
> colocation mystateful-ms-loc inf: mystateful-ms:Master myprim

This should be:

colocation mystateful-ms-loc inf: mystateful-ms:Master myprim:Started



> _______________________________________________
> 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker

More information about the Pacemaker mailing list