andreas at hastexo
Oct 23, 2011, 3:24 PM
Post #2 of 2
(197 views)
Permalink
|
On 10/23/2011 09:39 PM, Nick Khamis wrote:
> The following works as expected:
>
> node mydrbd1 \
> attributes standby="off"
> node mydrbd2 \
> attributes standby="off"
> primitive myIP ocf:heartbeat:IPaddr2 \
> op monitor interval="60" timeout="20" \
> params ip="192.168.2.5" cidr_netmask="24" \
> nic="eth1" broadcast="192.168.2.255" \
> lvs_support="true"
> primitive myDRBD ocf:linbit:drbd \
> params drbd_resource="r0.res" \
> op monitor role=Master interval="10" \
> op monitor role=Slave interval="30"
> ms msMyDRBD myDRBD \
> meta master-max="1" master-node-max="1" \
> clone-max="2" clone-node-max="1" \
> notify="true" globally-unique="false"
> group MyServices myIP
> order drbdAfterIP \
> inf: myIP msMyDRBD
> location prefer-mysql1 MyServices inf: mydrbd1
> location prefer-mysql2 MyServices inf: mydrbd2
??????
> property $id="cib-bootstrap-options" \
> no-quorum-policy="ignore" \
> stonith-enabled="false" \
> expected-quorum-votes="5" \
> dc-version="1.1.6-9971ebba4494012a93c03b40a2c58ec0eb60f50c" \
> cluster-recheck-interval="0" \
> cluster-infrastructure="openais"
> rsc_defaults $id="rsc-options" \
> resource-stickiness="100"
>
> However, when modifying the order entry to:
>
> order drbdAfterIP \
> inf: myIP:promote msMyDRBD:start
>
> DRBD no longer works. And when adding the following colocation:
yes, the promote of the IP will never happen as it is a) only configured
as primitve and b) IPaddr2 does not support a promote action ... no IP
promote, no DRBD start ...
>
> colocation drbdOnIP \
> inf: MyServices msMyDRBD:Master
>
> none of the resources work.
tried removing those obscure two location constraints?
Regards,
Andreas
--
Need help with Pacemaker?
http://www.hastexo.com/now
|
signature.asc
