[Pacemaker] Changes in the colocation constraints?
Andrew Beekhof
andrew at beekhof.net
Wed May 27 09:56:08 EDT 2009
2009/5/27 Димитър Бойн <DBOYN at postpath.com>:
> Hi,
>
> I was trying to follow http://wiki.linux-ha.org/DRBD/HowTov2
>
>
>
> In the configuration for Floating Peers there is an idea for the following
> constrains:
>
>
>
> <rsc_colocation id="colo_drbd0_ip0" to="ip0" from="drbd0:0"
> score="infinity"/>
>
> <rsc_colocation id="colo_drbd0_ip1" to="ip1" from="drbd0:1"
> score="infinity"/>
>
>
>
> I believe the current Pacemaker syntax would translate the above to
> something like:
>
> <rsc_colocation id="colocate-drbd0-ip-c001drbd01a"
> rsc="ip-c001drbd01a" with-rsc="ms-drbd0:0" score="INFINITY"/>
>
> <rsc_colocation id="colocate-drbd0-ip-c001drbd01b"
> rsc="ip-c001drbd01b" with-rsc="ms-drbd0:1" score="INFINITY"/>
>
>
>
> How ever I am not able to insert the setting...
This isn't allowed in v1.0
This could be replaced with a colocation constraint between DRBD and a
clone'd IPaddr (with clone-max=2) that added the clone instance to a
base address. I'm not sure if such a resource exists yet, but it
wouldn't be hard to add to the existing one.
> Please consider the environment before printing this e-mail
Are there really people out there that print emails?
More information about the Pacemaker
mailing list