<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Le 20/09/2012 00:02, denis bonnenfant a
écrit :<br>
</div>
<blockquote cite="mid:505A4112.7010306@diderot.org" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
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>
</blockquote>
<br>
OK, it seems that live migration implies no ordering/colocation
constraints. I saw the serialize option in old threads, but found
no info in the 1.1 doc.<br>
<br>
So now how can I make my VMs to wait lvm to be available at
startup, and to start on the node with active lvm (migration
threshold ?). <br>
And in the reverse side, what will happen if a node goes to standby
? how to ensure that VMs will live-migrate *before* lvm/drbd will be
stopped ?<br>
<br>
Denis<br>
</body>
</html>