Re: [Pacemaker] Notification when a node is down
On 15 September 2014 16:49, David Vossel wrote:
>
> This might be a useful reference.
>
> http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html-single/Pacemaker_Explained/index.html#idm207039249856
I've been having trouble with this too, and I spent ages on the above
link trying to make it work.
I've got the MailTo resource setup as a clone on all nodes. I get
emails telling me when a resource moves to or away from a node. But I
get nothing at all if a resource has failed for some reason and just
ends up in the "stopped" state.
I can't get ClusterMon to work with email notifications. Looking
through the source I can't see how it can ever work.
Looking at "/usr/lib/ocf/resource.d/pacemaker/ClusterMon" the "start"
method runs a command like this:
${HA_SBIN_DIR}/crm_mon -p $OCF_RESKEY_pidfile -d -i $OCF_RESKEY_update
$OCF_RESKEY_extra_options -h $OCF_RESKEY_htmlfile"
The example in the documentation uses the "extra_options" parameter to
pass through the email settings.
But the man page for "crm_mon" doesn't say anything about -T, -F, or
-P options! crm_mon has no ability at all to send email. I
eventually gave up and assumed that the documentation for this feature
was either out of date or just plain wrong.
This is with Pacemaker 1.1.10 from CentOS7 default repository.
pacemaker-cli-1.1.10-32.el7_0.x86_64
If the documentation for email notifications (7.2) *is* correct, then
could someone give me a hint as to what I'm doing wrong?
Thanks!
___
Pacemaker mailing list: Pacemaker@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
Re: [Pacemaker] KVM live migration with pcs
On 12 September 2014 12:34, Steven Hale wrote: > # pcs resource move vm-resource newnode Additionally, you must have the "allow-migrate=true" meta option set if you want to use live migration. Otherwise it will shutdown the resource and restart it on the new node, just like any other normal resource. ___ Pacemaker mailing list: Pacemaker@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
Re: [Pacemaker] KVM live migration with pcs
On 12 September 2014 12:24, Саша Александров wrote: > Is it possible to live migrate KVM with pcs? There is no 'pcs resource > migrate'. VirtualDomain RA has migrate_to/migrate_from functions, but what > is the method for cluster to call them? The command is "move" rather than "migrate". move [destination node] [--master] Move resource off current node (and optionally onto destination node). If --master is used the scope of the command is limited to the master role and you must use the master id (instead of the resource id). # pcs resource move vm-resource newnode ___ Pacemaker mailing list: Pacemaker@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
[Pacemaker] Fwd: VirtualDomain broken for live migration.
Dear all,
I'm in the process of setting up my first four-node cluster. I'm
using CentOS7 with PCS/Pacemaker/Corosync.
I've got everything set up with shared storage using GlusterFS. The
cluster is running and I'm in the process of adding resources. My
intention for the cluster is to use it to host virtual machines. I
want the cluster to be able to live-migrate VMs between hosts. I'm
not interested in monitoring resources inside the guests, just knowing
that the guest is running or not is fine.
I've got all the virtualization working with libvirt using KVM. Live
migration works fine. Now I'm trying to make it work through the
cluster.
I am using the VirtualDomain resource in heartbeat. I can add and
remove VMs. It works. But the live migration feature is broken.
Looking at the source, the fault is on this line:
virsh ${VIRSH_OPTIONS} migrate --live $DOMAIN_NAME ${remoteuri} ${migrateuri}
I guess virsh must have changed at some point, because the "--live"
flag does not exist any more. I can make it work with the following
change
virsh ${VIRSH_OPTIONS} migrate --p2p --tunnelled $DOMAIN_NAME
${remoteuri} ${migrateuri}
This works, at least for my case where I'm tunnelling the migration
over SSH. But it's not a real bug fix because it's going to need
extra logic somewhere to determine whether it needs to add the
"--tunnelled" flag or not, and whatever other flags are required.
I see that the VirtualDomain resource hasn't been worked on in over
four years. Similarly the Wiki page has had no updated in this time.
http://www.linux-ha.org/wiki/VirtualDomain_%28resource_agent%29
Is this project still in active development? Is anyone actually
working on this? While I could do the work to fix the VirtualDomain
resource to work with the latest version of virsh, I don't see the
point if the project is dead. I gather Heartbeat became what is now
Pacemaker, but there doesn't seem to be a new up-to-date version of
VirtualDomain included with Pacemaker.
Indeed even the Pacemaker documentation seems completely out of date.
I spent hours working with ClusterMon and these pages
http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/ch07.html
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/High_Availability_Add-On_Reference/s1-eventnotification-HAAR.html
just trying to get my cluster to send notification emails. It was
only when I looked at the ClusterMon source and the man page for
crm_mon that I realised the documentation is completely wrong and
ClusterMon has no ability at all to send emails. The "extra_options"
field lists options that crm_mon doesn't even show as supported!
What does everybody else use for managing virtual machines on a
Pacemaker cluster? If heartbeat VirtualDomain is no longer supported,
can anyone point me in the direction of something is that is still in
development?
Thanks for any help and advice anyone can offer.
Steve.
___
Pacemaker mailing list: Pacemaker@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
