Re: [ClusterLabs] [Announce] libqb 1.0rc2 release (fixed subject)
On 02/02/16 11:05 +, Christine Caulfield wrote: > I am pleased to announce the second 1.0 release candidate release of > libqb. Huge thanks to all those who have contributed to this release. IIUIC, good news is that so far 1.0.0 is a drop-in replacement for 0.17.2. For convenience, there are EPEL/Fedora builds for testing: https://copr.fedorainfracloud.org/coprs/jpokorny/libqb/build/157747/ Specfile has already been changed akin to: https://github.com/ClusterLabs/libqb/pull/174 EPEL5 builds omitted as they fail due to autoconf being too ancient (i.e., not because of the changes in the mentioned PR). -- Jan (Poki) pgpidN4jJI6_f.pgp Description: PGP signature ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [ClusterLabs] kvm live migration, resource moving
Hi Rasca, Because the command 'virsh migrate --live' command will move the vm without shutting down the guest operating system. It transfers the running state of the vm from one host to another. -Kyle - Original Message - From: "RaSca" To: "users" Sent: Wednesday, February 3, 2016 11:54:12 AM Subject: Re: [ClusterLabs] kvm live migration, resource moving It is not clear to me why you need to do things by hand. Why are you using virsh once you could do a resource move within the cluster? -- RaSca Mia Mamma Usa Linux: Niente è impossibile da capire, se lo spieghi bene! ra...@miamammausalinux.org http://www.miamammausalinux.org Il giorno 3/2/2016 14:47:28, Kyle O'Donnell ha scritto: > Hi, > > (apologies for cross posting, got a note that the pacemaker list is dead) > > 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 > > ___ > Users mailing list: Users@clusterlabs.org > http://clusterlabs.org/mailman/listinfo/users > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org > ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [ClusterLabs] kvm live migration, resource moving
It is not clear to me why you need to do things by hand. Why are you using virsh once you could do a resource move within the cluster? -- RaSca Mia Mamma Usa Linux: Niente è impossibile da capire, se lo spieghi bene! ra...@miamammausalinux.org http://www.miamammausalinux.org Il giorno 3/2/2016 14:47:28, Kyle O'Donnell ha scritto: > Hi, > > (apologies for cross posting, got a note that the pacemaker list is dead) > > 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 > > ___ > Users mailing list: Users@clusterlabs.org > http://clusterlabs.org/mailman/listinfo/users > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org > ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[ClusterLabs] kvm live migration, resource moving
Hi, (apologies for cross posting, got a note that the pacemaker list is dead) 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 ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[ClusterLabs] resource-agents 3.9.7 released
Hi, We've tagged today (Feb 3) a new stable resource-agents release (3.9.7) in the upstream repository. Big thanks go to all contributors! Needless to say, without you this release would not be possible. It has been a year since release v3.9.6, hence the number of changes is quite big. Still, every precaution has been taken not to introduce regressions. These are the most significant new features in the linux-ha set: - new resource agents: redis rabbitmq-cluster nagios The full list of changes for the linux-ha RA set is available in ChangeLog (https://github.com/ClusterLabs/resource-agents/blob/v3.9.7/ChangeLog) Use the agents introduced with this release with due care: they probably haven't got a lot of field testing. Please upgrade at the earliest opportunity. Best, The resource-agents maintainers ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
