First up, before I begin, I am looking to pacemaker for the future as
well and do not yet use it. So please take whatever I say about
pacemaker with a grain of sand. Andrew, on the other hand, is the author
and anything he says can be taken as authoritative on the topic.
On the future;
I also
Just to close out this thread, sanlock should be used to ensure a VM is only
running on one node at a time:
http://libvirt.org/locking.html
https://access.redhat.com/site/solutions/186853
Devin
On Apr 19, 2013, at 10:15 AM, Devin Bougie wrote:
> On Apr 18, 2013, at 5:54 PM, Digimer wrote:
>>
Andrew and Digimer,
Thank you for taking the time to respond, you have collaborated some of
what I've been putting together as the likely direction.
I am working on adapting some cluster-aware storage features for use in a
Linux cluster environment. With this kind of project it is useful to try
an
Once your VM is under cluster control, you should use the cluster commands
to start, stop or migrate it. Using a combination of Cluster and virsh
commands can result in a corrupt VM disk image as you can end up with the
VM running on multiple nodes at the same time.
I messed this up once while bui
On 04/23/2013 06:11 AM, Ralf Aumueller wrote:
Hello,
we have two 2-node clusters running on CentOS 6.4. Only service managed by
clusters are KVM virtual machines. Both clusters have access to an NFS-server on
which the config and storage files of the VMs reside.
Now I want to move a VM from clus
Hello,
we have two 2-node clusters running on CentOS 6.4. Only service managed by
clusters are KVM virtual machines. Both clusters have access to an NFS-server on
which the config and storage files of the VMs reside.
Now I want to move a VM from cluster1 to cluster2 with the following approach:
O
