Kyle O'Donnell
2016-02-03 13:11:14 UTC
Hi,
I'm using the predefined VirtualDomain resource type to mange kvm guests with
pacemaker. I am trying to sort out the best way I can use the built-in live
migration function within virsh:
# virsh migrate --live guest qemu+ssh://destination-host/system
Currently, I have to disable monitoring for the resource, run the live
migrate, do maintenance on the original host, live migrate back, enable
monitoring. Which is fine if I plan on migrating the guest back to the
original host, but when I want to permanently move a guest from one host to
another I need to be able to tell the cluster, heh I've already moved this
from A to B, please start monitoring on B.
Ideas?
Thanks,
Kyle
_______________________________________________
Pacemaker mailing list: ***@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
I'm using the predefined VirtualDomain resource type to mange kvm guests with
pacemaker. I am trying to sort out the best way I can use the built-in live
migration function within virsh:
# virsh migrate --live guest qemu+ssh://destination-host/system
Currently, I have to disable monitoring for the resource, run the live
migrate, do maintenance on the original host, live migrate back, enable
monitoring. Which is fine if I plan on migrating the guest back to the
original host, but when I want to permanently move a guest from one host to
another I need to be able to tell the cluster, heh I've already moved this
from A to B, please start monitoring on B.
Ideas?
Thanks,
Kyle
_______________________________________________
Pacemaker mailing list: ***@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org