Dmitry Koterov dmitry.kote...@gmail.com napisał:
Hello.
I have 3-node cluster managed by corosync+pacemaker+crm. Node1 and
Node2
are DRBD master-slave, also they have a number of other services
installed
(postgresql, nginx, ...). Node3 is just a corosync node (for quorum),
no
I think the suggestion was to put shooting the host in the fencing path of a
VM. This way if you can't get the host to fence the VM (as the host is already
dead) you just check if the host was fenced.
Daniel Dehennin daniel.dehen...@baby-gnu.org napisał:
Andrei Borzenkov arvidj...@gmail.com
Hanging corosync sounds like libqb problems: trusty comes with 0.16, which
likes to hang from time to time. Try building libqb 0.17.
Daniel Dehennin daniel.dehen...@baby-gnu.org napisał:
Hello,
I just have an issue on my pacemaker setup, my dlm/clvm/gfs2 was
blocked.
The “dlm_tool ls” command
Tomasz Kontusz tomasz.kont...@gmail.com:
Hi
I'm setting up a cluster which will use OpenVZ containers for
separating resource's environments.
So far I see it like this:
* each node runs Pacemaker
* each container runs pacemaker_remote, and one kind of resource
(but there might be multiple
to have IPaddr2 resource started on the node that holds container
with current pgsql master.
How can I go about achieving something like that?
Is the idea of using pacemaker_remote in such setup sensible?
--
Tomasz Kontusz
___
Pacemaker mailing list
(they are in separate subnet), and i wanted to avoid
nodes acting as routers.
A related question is how to set anti-colocation by HW node (so I'll have
database master and apps on different nodes if possible)?
2014-02-15 19:40 GMT+01:00 Tomasz Kontusz tomasz.kont...@gmail.com:
Hi
I'm setting up
