Hi,

I'm new to linux-ha, I've been able to test a 2 nodes setup running
drbd, lvm and ipaddr2 ressources in r1 and crm mode.

I'm using heartbeat+pacemaker from the binary repository on debian
etch.

I'm now trying this setup :
- 2 drbd nodes having ocf/{drbd,lvm,ipaddr2} resources
- 3 nodes with no resource assigned for the moment

the 2 drbd nodes :
- drbd utils, correctly configured drbd.conf and drbd kernel module
- 3 nics (eth0, eth1, eth2)

the 3 other nodes :
- don't know anything about drbd (the
  OCF_ROOT/resource.d/heartbeat/drbd script is there though)
- only have 1 nic (eth0)
 
My first attempt is to run one drbd resource on the 2 drbd nodes only.
The resource is created in stopped target role.
when i add the resource definition, every node does a monitor check,
on the 3 other nodes it fails, the ocf drbd script returns 5 and
the resource get stuck trying to monitor on the other nodes. 
In that case the workaround is to install drbd-utils on the 3 other
nodes so that the ocf drbd script returns 7.

it does not look like the correct behavior to me. is it normal ?


next attempt is to run 4 drbd resources, and a group of lvm + 3
ipaddr2 resources. (3 ipaddr2 resources because the drbd nodes have 3
nics)

on the 3 other nodes i'm using the workaround so that ocf drbd script
returns 7.
But the next issue is that the 3 other nodes only have 1 nic so the
ipaddr2 script fails and resources get stuck again.

I'm not really sure heartbeart/pacemaker are meant to be used in that
kind of situation.
Does it make sense ?
What I am doing wrong ?
Are you able to reproduce this behavior ?
Help ! ;-)

here are the constaints/resources i'm using on top of default
settings.

first attempt:

Attachment: test-c.xml
Description: XML document

Attachment: test-r.xml
Description: XML document

the last one:

Attachment: constraints.xml
Description: XML document

Attachment: resources.xml
Description: XML document

English is not my native language, i'm not sure I achieved to
correctly express my complex needs :)

TIA

-- 
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to