Il giorno Ven 14 Mag 2010 13:34:35 CET, Andrew Beekhof ha scritto:
> On Fri, May 14, 2010 at 12:55 PM, RaSca<[email protected]> wrote:
>> Hi all,
>> why even if I've declared these location directives:
>>
>> location cli-prefer-share-a share-a \
>> rule $id="cli-prefer-rule-share-a" 200: #uname eq ubuntu-nodo1
>> location cli-prefer-share-b share-b \
>> rule $id="cli-prefer-rule-share-b" 200: #uname eq ubuntu-nodo2
>> location clisec-prefer-share-a share-a \
>> rule $id="clisec-prefer-rule-share-a" 0: #uname eq ubuntu-nodo2
>> location clisec-prefer-share-b share-b \
>> rule $id="clisec-prefer-rule-share-b" 0: #uname eq ubuntu-nodo1
>>
>> when the cluster comes up those resources runs only on the DC without
>> considering the location I've defined?
>
> Both nodes start at the same time?
I turn up a node, then the other one. It's not the exact same time, I
wait until the first corosync is up.
>> Also, it's impossible to move a resource after it is up on the DC.
>> It's a stickiness problem? What I am missing?
> Please show us the complete config.
Here it is, I've got two drbds with a filesystem and a IP:
node ubuntu-nodo1 \
attributes standby="off"
node ubuntu-nodo2 \
attributes standby="off"
primitive drbd0 ocf:linbit:drbd \
params drbd_resource="r0" \
op monitor interval="20s" \
meta target-role="Started"
primitive drbd1 ocf:linbit:drbd \
params drbd_resource="r1" \
op monitor interval="20s" \
meta target-role="Started"
primitive pingd ocf:pacemaker:pingd \
params host_list="192.168.1.1 192.168.1.2" multiplier="100" \
op monitor interval="20smeta" target-role="Started"
primitive share-a-fs ocf:heartbeat:Filesystem \
params device="/dev/drbd0" directory="/share-a" fstype="ext3" \
op monitor interval="20smeta" target-role="Started"
primitive share-a-ip ocf:heartbeat:IPaddr2 \
params ip="192.168.1.33" nic="eth0" \
op monitor interval="20smeta" target-role="Started"
primitive share-b-fs ocf:heartbeat:Filesystem \
params device="/dev/drbd1" directory="/share-b" fstype="ext3" \
op monitor interval="20smeta" target-role="Started"
primitive share-b-ip ocf:heartbeat:IPaddr2 \
params ip="192.168.1.34" nic="eth0" \
op monitor interval="20smeta" target-role="Started"
group share-a share-a-ip share-a-fs \
meta target-role="Started"
group share-b share-b-ip share-b-fs \
meta target-role="Started"
ms ms_drbd0 drbd0 \
meta master-max="1" master-node-max="1" clone-max="2"
clone-node-max="1" notify="true"
ms ms_drbd1 drbd1 \
meta master-max="1" master-node-max="1" clone-max="2"
clone-node-max="1" notify="true"
clone pingd_clone pingd \
meta globally-unique="false" target-role="Started"
location cli-prefer-share-a share-a \
rule $id="cli-prefer-rule-share-a" inf: #uname eq ubuntu-nodo1 and
#uname eq ubuntu-nodo1
location cli-prefer-share-b share-b \
rule $id="cli-prefer-rule-share-b" 200: #uname eq ubuntu-nodo2
location clisec-prefer-share-a share-a \
rule $id="clisec-prefer-rule-share-a" 0: #uname eq ubuntu-nodo2
location clisec-prefer-share-b share-b \
rule $id="clisec-prefer-rule-share-b" 0: #uname eq ubuntu-nodo1
location share-a_on_connected_node share-a \
rule $id="share-a_on_connected_node-rule" -inf: not_defined pingd or
pingd lte 0
location share-b_on_connected_node share-b \
rule $id="share-b_on_connected_node-rule" -inf: not_defined pingd or
pingd lte 0
colocation share-a_on_ms_drbd0 200: share-a ms_drbd0:Master
colocation share-b_on_ms_drbd1 200: share-b ms_drbd1:Master
order share-a_after_ms_drbd0 inf: ms_drbd0:promote share-a:start
order share-b_after_ms_drbd1 inf: ms_drbd1:promote share-b:start
property $id="cib-bootstrap-options" \
dc-version="1.0.8-042548a451fce8400660f6031f4da6f0223dd5dd" \
cluster-infrastructure="openais" \
no-quorum-policy="ignore" \
stonith-enabled="false" \
default-resource-stickiness="INFINITY" \
expected-quorum-votes="2" \
Thanks a lot for your help!
--
RaSca
Mia Mamma Usa Linux: Niente รจ impossibile da capire, se lo spieghi bene!
[email protected]
http://www.miamammausalinux.org
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
