Le 20/09/2012 00:02, denis bonnenfant a écrit :
Hi,
I have an issue with live migration of a xen resource over a clvm vg :
- a lvm vg (cl_LVM1) cloned resource is defined on both nodes,
- a xen resource (res_Xen_dns4) is using a lv from vg1, availiable on
both nodes,
- a colocation
Hi,
I have an issue with live migration of a xen resource over a clvm vg :
- a lvm vg (cl_LVM1) cloned resource is defined on both nodes,
- a xen resource (res_Xen_dns4) is using a lv from vg1, availiable on
both nodes,
- a colocation constraint is defined between domu and vg1
When I try t
Le 15/09/2012 22:34, denis bonnenfant a écrit :
Le 15/09/2012 18:23, denis bonnenfant a écrit :
Hello,
do I need to start pacemaker from corosync config too ?
http://theclusterguy.clusterlabs.org/post/907043024/introducing-the-pacemaker-master-control-process-for
seems to suggest that in my
Le 15/09/2012 18:23, denis bonnenfant a écrit :
Hello,
I'm currently running in production a 3-nodes
corosync/pacemaker/drbd/clvm xen virtualisation cluster, based on
debian wheezy.
Two nodes are running drbd inactive/active setup,
Sorry for the typo it's active/active !
with
Hello,
I'm currently running in production a 3-nodes
corosync/pacemaker/drbd/clvm xen virtualisation cluster, based on debian
wheezy.
Two nodes are running drbd inactive/active setup, with clustered VGs
(/dev/xen-data) on top of drbd disk for local domUs , and ISCSI target
LV ( /dev/xen-da
