On 23/06/14 12:50 PM, Kostiantyn Ponomarenko wrote:
Digimer,
I am using Debian as OS and Corosync + Pacemaker as cluster stack.
I understand your suggestion.
I don't have any questions about it.
My main question is how to do it automatically?
So that it could work without human interruption for
Digimer,
I am using Debian as OS and Corosync + Pacemaker as cluster stack.
I understand your suggestion.
I don't have any questions about it.
My main question is how to do it automatically?
So that it could work without human interruption for a while (nodes could
be rebooted, but not repaired).
Hi Kostya,
I'm having a little trouble understanding your question, sorry.
On boot, the node will not start anything, so after booting it, you
log in, check that it can talk to the peer node (a simple ping is
generally enough), then start the cluster. It will join the peer's
existing clus
Hi Digimer,
Suppose I disabled to cluster on start up, but what about remaining node,
if I need to reboot it?
So, even in case of connection lost between these two nodes I need to have
one node working and providing resources.
How did you solve this situation?
Should it be a separate daemon which
On 23/06/14 09:11 AM, Kostiantyn Ponomarenko wrote:
Hi guys,
I want to gather all possible configuration variants for 2-node cluster,
because it has a lot of pitfalls and there are not a lot of information
across the internet about it. And also I have some questions about
configurations and their
Hi guys,
I want to gather all possible configuration variants for 2-node cluster,
because it has a lot of pitfalls and there are not a lot of information
across the internet about it. And also I have some questions about
configurations and their specific problems.
VARIANT 1:
-
We
