[Pacemaker] live migration and colocation with lvm cloneset issue
denis bonnenfant
denis.bonnenfant at diderot.org
Wed Sep 19 22:02:58 UTC 2012
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 to live migrate res_Xen_dns4 from crm, it stops and restarts
cloned instances of vg1, swapping them between nodes ! underlying drbd
is demoted... Of course, this operation crashes all the other VMs
connected to vg1, and finally all the cluster is fencing...
Maybe I'm completely wrong, but I don't understand this behavior ! I
guessed that the colocation constraints were defined with any clone
member, and didn't force the clones to move. Did I missed something
important ?
Thanks in advance for any help,
Denis
the relevant cib is something like :
primitive res_LVM_1 ocf:heartbeat:LVM \
params volgrpname="xen-data" \
operations $id="res_LVM_1-operations" \
op start interval="0" timeout="30" \
op stop interval="0" timeout="30" \
op monitor interval="10" timeout="60" start-delay="0" \
op methods interval="0" timeout="5" \
meta target-role="started"
primitive res_Xen_dns4 ocf:heartbeat:Xen \
params xmfile="/etc/xen/dns4.diderot.org"
allow_mem_management="false" \
operations $id="res_Xen_dns4-operations" \
op start interval="0" timeout="60" \
op stop interval="0" timeout="40" \
op monitor interval="10" timeout="30" start-delay="0" \
op migrate_from interval="0" timeout="120" \
op migrate_to interval="0" timeout="120" \
meta allow-migrate="true"
**clone cl_LVM_1 res_LVM_1 \
meta clone-max="2" notify="true" interleave="true"
resource-stickiness="100"
**colocation col_res_Xen_dns4_cl_LVM_1 inf: res_Xen_dns4 cl_LVM_1
order ord_cl_LVM_1_res_Xen_dns4 inf: cl_LVM_1 res_Xen_dns4
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20120920/1033b841/attachment-0003.html>
More information about the Pacemaker
mailing list