[Pacemaker] OpenVZ live migration
mailing list
mailing.list1111 at gmail.com
Mon Dec 15 20:33:34 UTC 2014
Hello Everybody,
I need your help with the set up the live migration on cluster with two
nodes and two virtual machine.
I have this set up:
node nodea \
attributes standby="off"
node nodeb \
attributes standby="off"
primitive drbd1 ocf:linbit:drbd \
params drbd_resource="drbd1" \
operations $id="drbd1-operations" \
op monitor start-delay="0" interval="31" \
meta target-role="started"
primitive drbd2 ocf:linbit:drbd \
params drbd_resource="drbd2" \
operations $id="drbd2-operations" \
op monitor start-delay="0" interval="31" \
meta target-role="started"
primitive drbd3 ocf:linbit:drbd \
params drbd_resource="drbd3" \
operations $id="drbd3-operations" \
op monitor start-delay="0" interval="31" \
meta target-role="started"
primitive fs_drbd1 ocf:heartbeat:Filesystem \
params device="/dev/drbd1" directory="/mnt/drbd1" fstype="ext4"
options="noatime" \
meta target-role="started"
primitive fs_drbd2 ocf:heartbeat:Filesystem \
params device="/dev/drbd2" directory="/mnt/drbd2" fstype="ext4"
options="noatime" \
meta target-role="started"
primitive fs_drbd3 ocf:heartbeat:Filesystem \
params device="/dev/drbd3" directory="/mnt/drbd3" fstype="ext4"
options="noatime" \
meta target-role="started"
primitive res_ManageVE_101 ocf:heartbeat:ManageVE \
params veid="101" \
operations $id="res_ManageVE_101-operations" \
op start interval="0" timeout="75" \
op stop interval="0" timeout="75" \
op monitor interval="10" timeout="10" start-delay="0" \
op migrate_to interval="0" timeout="75" \
op migrate_from interval="0" timeout="75" \
meta target-role="started" allow-migrate="true" failure-timeout="5"
primitive res_ManageVE_102 ocf:heartbeat:ManageVE \
params veid="102" \
operations $id="res_ManageVE_102-operations" \
op start interval="0" timeout="75" \
op stop interval="0" timeout="75" \
op monitor interval="11" timeout="10" start-delay="0" \
op migrate_to interval="0" timeout="75" \
op migrate_from interval="0" timeout="75" \
meta target-role="started" allow-migrate="true" failure-timeout="5"
primitive res_vz_vz_clone lsb:vz \
operations $id="res_vz_vz_clone-operations" \
op start interval="0" timeout="15" \
op stop interval="0" timeout="15" \
op monitor interval="15" timeout="15" start-delay="15"
ms ms_drbd1 drbd1 \
meta clone-max="2" notify="true" target-role="started"
allow-migrate="true"
ms ms_drbd2 drbd2 \
meta clone-max="2" notify="true" target-role="started"
allow-migrate="true"
ms ms_drbd3 drbd3 \
meta clone-max="2" notify="true" target-role="started"
allow-migrate="true"
clone cl_vz_1 res_vz_vz_clone \
meta clone-max="2" notify="true" interleave="true"
location loc_fs_drbd1_jupiter fs_drbd1 2: nodea
location loc_fs_drbd1_mars fs_drbd1 0: nodeb
location loc_fs_drbd2_jupiter fs_drbd2 0: nodea
location loc_fs_drbd2_mars fs_drbd2 2: nodeb
location loc_fs_drbd3_jupiter fs_drbd3 0: nodea
location loc_fs_drbd3_mars fs_drbd3 2: nodeb
location loc_ms_drbd1_jupiter ms_drbd1 2: nodea
location loc_ms_drbd1_mars ms_drbd1 0: nodeb
location loc_ms_drbd2_jupiter ms_drbd2 0: nodea
location loc_ms_drbd3_jupiter ms_drbd2 0: nodea
location loc_ms_drbd3_mars ms_drbd2 2: nodeb
colocation fs_drbd1_colo inf: fs_drbd1 ms_drbd1:Master
colocation fs_drbd2_colo inf: fs_drbd2 ms_drbd2:Master
colocation fs_drbd3_colo inf: fs_drbd3 ms_drbd3:Master
colocation vz_drbd1_colo inf: res_ManageVE_101 fs_drbd1
colocation vz_drbd2_colo inf: res_ManageVE_102 fs_drbd2
order fs_after_drbd1 inf: ms_drbd1:promote fs_drbd1:start
order fs_after_drbd2 inf: ms_drbd2:promote fs_drbd2:start
order fs_after_drbd3 inf: ms_drbd3:promote fs_drbd3:start
order vz_after_fs1 inf: fs_drbd1 res_ManageVE_101:start
order vz_after_fs2 inf: fs_drbd2 res_ManageVE_102:start
property $id="cib-bootstrap-options" \
expected-quorum-votes="2" \
stonith-enabled="false" \
dc-version="1.1.7-ee0730e13d124c3d58f00016c3376a1de5323cff" \
no-quorum-policy="ignore" \
cluster-recheck-interval="15" \
cluster-infrastructure="openais" \
last-lrm-refresh="1412925565" \
start-failure-is-fatal="false"
When I shutdown the nodea that the resource get on the nodeb, bad when I
switch nodea again on, that the cluster kill the virtual and start it on
the nodea. It's here a Idea how to allow live migrate on the cluster?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20141215/c7962ef0/attachment-0003.html>
More information about the Pacemaker
mailing list