On Wed, 20 Mar 2013, Andreas Kurz wrote:
On 2013-03-19 17:02, Quentin Smith wrote:
Hi-
I have my cluster configured to use a cloned ping resource, such that I
can write a constraint that I prefer resources to run on a node that has
network connectivity. That works fine if a machine loses its
Hi-
I have my cluster configured to use a cloned ping resource, such that I
can write a constraint that I prefer resources to run on a node that has
network connectivity. That works fine if a machine loses its network
connection (the ping attribute goes to 0, resources migrate to another
mach
On Sat, 24 Apr 2010, Paul Gear wrote:
On 24/04/10 15:05, Quentin Smith wrote:
Hi Paul,
Current clvm actually supports multiple locking schemes, including both
the old redhat cluster stack and modern corosync/openais. We use Ubuntu
Hardy with backported corosync and clvm packages, and it works
Hi Paul,
Current clvm actually supports multiple locking schemes, including both
the old redhat cluster stack and modern corosync/openais. We use Ubuntu
Hardy with backported corosync and clvm packages, and it works pretty
well. Hand-backporting is not for the faint of heart, though.
--Quent
go. It was fixed in
http://hg.clusterlabs.org/pacemaker/stable-1.0/rev/214f0fc258f2.
Thanks
On Fri, Mar 12, 2010 at 2:36 PM, Quentin Smith wrote:
Hi-
I just took the latest updates to pacemaker and heartbeat from
http://people.debian.org/~madkiss/ha. In particular, I upgraded
heartbeat 1:3
Hi-
I just took the latest updates to pacemaker and heartbeat from
http://people.debian.org/~madkiss/ha. In particular, I upgraded
heartbeat 1:3.0.2-1~bpo50+1 to 1:3.0.2+hg12547-2~bpo50+1
pacemaker 1.0.7+hg20100203-1~bpo50+1 to 1.0.7+hg20100303r15404-3~bpo50+1
cluster-agents 1:1.0.2-1~bpo50+1
