<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi, <br>
<br>
I have an issue with live migration of a xen resource over a clvm
vg : <br>
<br>
- a lvm vg (cl_LVM1) cloned resource is defined on both nodes, <br>
- a xen resource (res_Xen_dns4) is using a lv from vg1, availiable
on both nodes,<br>
- a colocation constraint is defined between domu and vg1<br>
<br>
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... <br>
<br>
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 ?<br>
<br>
Thanks in advance for any help, <br>
<br>
Denis <br>
<br>
<br>
<br>
<br>
the relevant cib is something like : <br>
<br>
primitive res_LVM_1 ocf:heartbeat:LVM \<br>
params volgrpname="xen-data" \<br>
operations $id="res_LVM_1-operations" \<br>
op start interval="0" timeout="30" \<br>
op stop interval="0" timeout="30" \<br>
op monitor interval="10" timeout="60" start-delay="0" \<br>
op methods interval="0" timeout="5" \<br>
meta target-role="started"<br>
primitive res_Xen_dns4 ocf:heartbeat:Xen \<br>
params xmfile="/etc/xen/dns4.diderot.org"
allow_mem_management="false" \<br>
operations $id="res_Xen_dns4-operations" \<br>
op start interval="0" timeout="60" \<br>
op stop interval="0" timeout="40" \<br>
op monitor interval="10" timeout="30" start-delay="0" \<br>
op migrate_from interval="0" timeout="120" \<br>
op migrate_to interval="0" timeout="120" \<br>
meta allow-migrate="true"<br>
<font size="2"><b></b></font>clone cl_LVM_1 res_LVM_1 \<br>
meta clone-max="2" notify="true" interleave="true"
resource-stickiness="100"<br>
<font size="2"><b></b></font>colocation col_res_Xen_dns4_cl_LVM_1
inf: res_Xen_dns4 cl_LVM_1<br>
order ord_cl_LVM_1_res_Xen_dns4 inf: cl_LVM_1 res_Xen_dns4<br>
<br>
</body>
</html>