Re: [Pacemaker] pacemaker-remote debian wheezy

2015-03-14 Thread Kostiantyn Ponomarenko
Hi Alexis, Sorry, I didn't work with drbd. Try to look here http://clusterlabs.org/doc/en-US/Pacemaker/1.1-crmsh/html-single/Clusters_from_Scratch/ . Thank you, Kostya ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/

Re: [Pacemaker] Call cib_apply_diff failed (-205): Update was older than existing configuration

2015-02-09 Thread Kostiantyn Ponomarenko
Hi Kristoffer, Thank you for the help. I will let you know if I see the same with the latest version. On Feb 9, 2015 10:07 AM, "Kristoffer Grönlund" wrote: > Hi, > > Kostiantyn Ponomarenko writes: > > > Hi guys, > > > > I saw this during applying the

Re: [Pacemaker] Call cib_apply_diff failed (-205): Update was older than existing configuration

2015-02-05 Thread Kostiantyn Ponomarenko
3182] isis-seth943f pacemakerd: notice: pcmk_shutdown_worker:Shuting down Pacemaker Thank you, Kostya On Thu, Feb 5, 2015 at 6:15 PM, Kostiantyn Ponomarenko < konstantin.ponomare...@gmail.com> wrote: > Hi guys, > > I saw this during applying the configuration using a script with crmsh

[Pacemaker] Call cib_apply_diff failed (-205): Update was older than existing configuration

2015-02-05 Thread Kostiantyn Ponomarenko
Hi guys, I saw this during applying the configuration using a script with crmsh commands: + crm configure primitive STONITH_node-1 stonith:fence_avid_sbb_hw + crm configure primitive STONITH_node-0 stonith:fence_avid_sbb_hw params delay=10 + crm configure location dont_run_STONITH_node-1_on_node-

Re: [Pacemaker] authentication in the cluster

2015-02-05 Thread Kostiantyn Ponomarenko
Chrissie, thank you! =) It helps! Thank you, Kostya On Thu, Feb 5, 2015 at 3:59 PM, Christine Caulfield wrote: > On 02/05/2015 01:47 PM, Kostiantyn Ponomarenko wrote: > > Chrissie, one more thing. > > > > And I also suppose that the key is read only one time at the start-u

Re: [Pacemaker] authentication in the cluster

2015-02-05 Thread Kostiantyn Ponomarenko
Chrissie, one more thing. And I also suppose that the key is read only one time at the start-up of the Corosync. In other words there is no any check for the presence of the key or its update, while Corosync is working. Am I right? Thank you, Kostya On Thu, Feb 5, 2015 at 2:42 PM, Kostiantyn

Re: [Pacemaker] authentication in the cluster

2015-02-05 Thread Kostiantyn Ponomarenko
Hi Chrissie, On Thu, Jan 29, 2015 at 11:44 AM, Christine Caulfield wrote: > as corosync rejects the messages > with the wrong authkey > And I suppose that it is enough just to use "crypto_hash" option. I am right? Thank you, Kostya ___ Pacemaker mail

Re: [Pacemaker] authentication in the cluster

2015-01-27 Thread Kostiantyn Ponomarenko
Hi Chrissie, I know that this setup it crazy thing =) First of all I needed to say - think about each two-node cluster as one box with two nodes. > You can't connect clusters together like that. I know that. >All nodes in the cluster have just 1 authkey file. That is true. But in this example th

[Pacemaker] authentication in the cluster

2015-01-27 Thread Kostiantyn Ponomarenko
Hi all, Here is a situation - there are two "two-node" clusters. They have totally identical configuration. Nodes in the clusters are connected directly, without any switches. Here is a part of corosync.comf file: totem { version: 2 cluster_name: mycluster transport: udpu crypto_hash: sha256 c

[Pacemaker] rrp_mode in corosync.conf

2015-01-27 Thread Kostiantyn Ponomarenko
Hi all, I've been looking for a good answer to my question, but all information I found is ambiguous. I hope to get a good answer here =) The only description about "active" and "passive" modes I found is: Active: both rings will be active, in use Passive: only one of the 2 rings is in us

Re: [Pacemaker] Corosync fails to start when NIC is absent

2015-01-20 Thread Kostiantyn Ponomarenko
t; By that I mean that as long as you don't shutdown interface everything > will work as expected. Interface shutdown is administrator decision, > system doesn't do it automagically :) > > Regards, > Honza > > > > > Thank you, > > Kostya > &

Re: [Pacemaker] Corosync fails to start when NIC is absent

2015-01-19 Thread Kostiantyn Ponomarenko
One more thing to clarify. You said "rebind can be avoided" - what does it mean? Thank you, Kostya On Wed, Jan 14, 2015 at 1:31 PM, Kostiantyn Ponomarenko < konstantin.ponomare...@gmail.com> wrote: > Thank you. Now I am aware of it. > > Thank you, > Kostya > >

Re: [Pacemaker] pacemaker-remote debian wheezy

2015-01-15 Thread Kostiantyn Ponomarenko
Thomas, There was a need for me to run the latest cluster stuff on Debian 7. So I created a document for myself to use. I don't claim this doc to be the best way to go, but it works for me. I hope it will work for you as well. Here is the doc's content: Software - libqb 0.17.0 -

Re: [Pacemaker] pacemaker-remote debian wheezy

2015-01-15 Thread Kostiantyn Ponomarenko
Hi Thomas, I don't remember starting from which version of Pacemaker "crmsh" is not included in it anymore. It goes as a independent product. You can get it back. Here is the link https://github.com/crmsh/crmsh/ . Build and install =) Thank you, Kostya On Thu, Jan 15, 2015 at 3:18 PM, Kristoffer

Re: [Pacemaker] Corosync fails to start when NIC is absent

2015-01-14 Thread Kostiantyn Ponomarenko
put in a standby mode > (shows: > >>> communication error), > >>> > >>> and it is possible that the cluster is running all resources, but > applied > >>> configuration is not guaranteed to be fully loaded (some rules can be > >>> missed). > >

Re: [Pacemaker] Corosync fails to start when NIC is absent

2015-01-13 Thread Kostiantyn Ponomarenko
see comments to the bug) the > > cluster will work, but in that case its working state is unstable and the > > cluster can stop working every moment. > > > > > > So, is it correct? Does my assumptions make any sense? I didn't any other > > explanation in

Re: [Pacemaker] Corosync fails to start when NIC is absent

2015-01-12 Thread Kostiantyn Ponomarenko
--- It is possible that in some rare cases (see comments to the bug) the cluster will work, but in that case its working state is unstable and the cluster can stop working every moment. So, is it correct? Does my assumptions make any sense? I didn't any other explanation

[Pacemaker] Corosync fails to start when NIC is absent

2015-01-09 Thread Kostiantyn Ponomarenko
Hi guys, Corosync fails to start if there is no such network interface configured in the system. Even with "rrp_mode: passive" the problem is the same when at least one network interface is not configured in the system. Is this the expected behavior? I thought that when you use redundant rings, i

Re: [Pacemaker] Only build crm_uuid when supporting heartbeat

2014-09-22 Thread Kostiantyn Ponomarenko
Fair enough, thank you! Thank you, Kostya On Mon, Sep 22, 2014 at 8:38 PM, Andrew Beekhof wrote: > > On 22 Sep 2014, at 11:50 pm, Kostiantyn Ponomarenko < > konstantin.ponomare...@gmail.com> wrote: > > > Hi guys, > > > > Could you help me to understand the

[Pacemaker] Only build crm_uuid when supporting heartbeat

2014-09-22 Thread Kostiantyn Ponomarenko
Hi guys, Could you help me to understand the reason to build "crm_uuid" only when supporting heartbeat? My situation is the next, I am trying to build Pacemaker's sources for Debian. I built the sources from Debian Wheezy repo (removed "--with-heartbeat" from it). Then I did the same but using so

[Pacemaker] testquorum module

2014-07-01 Thread Kostiantyn Ponomarenko
Hi Chrissie, You mentioned "testquorum" in your doc ("Whatever happened to cman") as it's a good place if you are thinking about writing your own quorum module. The only file I found in corosync code is in /test folder and I think it's not the module. Could you please point me where I can find thi

Re: [Pacemaker] What is the cman package for ubuntu 13.10

2014-06-25 Thread Kostiantyn Ponomarenko
Hi Vijay B, I have 2 Debian machines with the latest Corosync and Pacemaker. I wanted the latest versions of these packages, so I didn't use "apt-get install corosync pacemaker". Instead of that I downloaded the sources, built it and installed it. I have a document with all steps I did to get it w

Re: [Pacemaker] configuration variants for 2 node cluster

2014-06-24 Thread Kostiantyn Ponomarenko
Digimer, Yes, wait_for_all is a part of votequorum in Corosync v2. Thank you, Kostya On Tue, Jun 24, 2014 at 6:47 PM, Digimer wrote: > On 24/06/14 03:55 AM, Christine Caulfield wrote: > >> On 23/06/14 15:49, Digimer wrote: >> >>> Hi Kostya, >>> >>>I'm having a little trouble understanding

Re: [Pacemaker] configuration variants for 2 node cluster

2014-06-24 Thread Kostiantyn Ponomarenko
ine Caulfield wrote: > On 24/06/14 09:36, Kostiantyn Ponomarenko wrote: > >> Hi Chrissie, >> >> But wait_for_all doesn't help when there is no connection between the >> nodes. >> Because in case I need to reboot the remaining working node I won't get >

Re: [Pacemaker] configuration variants for 2 node cluster

2014-06-24 Thread Kostiantyn Ponomarenko
for you, once >> setup properly. What operating system do you plan to use, and what >> cluster stack? I suspect it will be corosync + pacemaker, which should >> work fine. >> >> digimer >> >> On 23/06/14 10:36 AM, Kostiantyn Ponomarenko wrote: >> >&g

Re: [Pacemaker] configuration variants for 2 node cluster

2014-06-23 Thread Kostiantyn Ponomarenko
r to keep them >> down? >> >> Thank you, >> Kostya >> >> >> On Mon, Jun 23, 2014 at 4:34 PM, Digimer > <mailto:li...@alteeve.ca>> wrote: >> >> On 23/06/14 09:11 AM, Kostiantyn Ponomarenko wrote: >> >> Hi guys

Re: [Pacemaker] configuration variants for 2 node cluster

2014-06-23 Thread Kostiantyn Ponomarenko
checks somehow connection between the two nodes and decides to run corosync and pacemaker or to keep them down? Thank you, Kostya On Mon, Jun 23, 2014 at 4:34 PM, Digimer wrote: > On 23/06/14 09:11 AM, Kostiantyn Ponomarenko wrote: > >> Hi guys, >> I want to gather all poss

[Pacemaker] configuration variants for 2 node cluster

2014-06-23 Thread Kostiantyn Ponomarenko
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

Re: [Pacemaker] API documentation

2014-06-17 Thread Kostiantyn Ponomarenko
Andrew, many thanks! On Jun 18, 2014 2:11 AM, "Andrew Beekhof" wrote: > > On 17 Jun 2014, at 8:01 pm, Kostiantyn Ponomarenko < > konstantin.ponomare...@gmail.com> wrote: > > > I took a look at the include folders of pacemaker and corosync and I > didn'

[Pacemaker] API documentation

2014-06-17 Thread Kostiantyn Ponomarenko
I took a look at the include folders of pacemaker and corosync and I didn't find there any explanation to functions. Did I look at a wrong place? My goal is to manage cluster from my app, so I don't need to use crmsh or pcs. Any ideas are appreciated. _

Re: [Pacemaker] votequorum for 2 node cluster

2014-06-13 Thread Kostiantyn Ponomarenko
nly the node which doesn't have the lowest nodeid? Am I right? Thank you, Kostya On Thu, Jun 12, 2014 at 12:37 PM, Christine Caulfield wrote: > On 12/06/14 00:51, Andrew Beekhof wrote: > >> Chrissy? Can you shed some light here? >> >> On 11 Jun 2014, at

Re: [Pacemaker] votequorum for 2 node cluster

2014-06-11 Thread Kostiantyn Ponomarenko
the lowest nodeid we lose all. So I can lose only the node which doesn't have the lowest nodeid? And it's not useful in 2 node cluster. Am i correct? Thank you, Kostya On Wed, Jun 11, 2014 at 4:33 PM, Vladislav Bogdanov wrote: > 11.06.2014 16:26, Kostiantyn Ponomarenko wrote: &

[Pacemaker] votequorum for 2 node cluster

2014-06-11 Thread Kostiantyn Ponomarenko
Hi guys, I am trying to deal somehow with split brain situation in 2 node cluster using votequorum. Here is a quorum section in my corosync.conf: provider: corosync_votequorum expected_votes: 2 wait_for_all: 1 last_man_standing: 1 auto_tie_breaker: 1 My question is about behavior of the remainin

Re: [Pacemaker] auto_tie_breaker in two node cluster

2014-05-21 Thread Kostiantyn Ponomarenko
Honza, Can you please explain what does "network based" mean? Thank you, Kostya On Wed, May 21, 2014 at 10:54 AM, Jan Friesse wrote: > > I am not quite understand how auto_tie_breaker works. > > Say we have a cluster with 2 nodes and enabled auto_tie_breaker feature. > > Each node has 2 NICs.

[Pacemaker] auto_tie_breaker in two node cluster

2014-05-20 Thread Kostiantyn Ponomarenko
I am not quite understand how auto_tie_breaker works. Say we have a cluster with 2 nodes and enabled auto_tie_breaker feature. Each node has 2 NICs. One NIC is used for cluster communication and another one is used for providing some services from the cluster. So the question is how the nodes will