Re: [ClusterLabs] Master-Slaver resource Restarted after configuration change

On 06/28/2016 04:10 PM, Ilia Sokolinski wrote: > Feri, > > > > I have a follow-up question: > > We are trying to achieve an NDU for our Master/Slave resource - this is > why the resource parameter is being updated. > The desired sequence of events is as follows: > > 1. Resource parameter is

Re: [ClusterLabs] Master-Slaver resource Restarted after configuration change

Feri, I have a follow-up question: We are trying to achieve an NDU for our Master/Slave resource - this is why the resource parameter is being updated. The desired sequence of events is as follows: Resource parameter is updated in pacemaker. Slave instance is reloaded (or restarted) to pickup t

Re: [ClusterLabs] Default Behavior

On 28/06/16 11:53 AM, Pavlov, Vladimir wrote: > Hello! > > We have Pacemaker cluster of two node Active/Backup (OS Centos 6.7), > with resources IPaddr2 and ldirectord. > > Cluster Properties: > > cluster-infrastructure: cman > > dc-version: 1.1.11-97629de > > no-quorum-policy: ignore > > sto

Re: [ClusterLabs] Default Behavior

On 06/28/2016 10:53 AM, Pavlov, Vladimir wrote: > Hello! > > We have Pacemaker cluster of two node Active/Backup (OS Centos 6.7), > with resources IPaddr2 and ldirectord. > > Cluster Properties: > > cluster-infrastructure: cman > > dc-version: 1.1.11-97629de > > no-quorum-policy: ignore > > s

[ClusterLabs] Default Behavior

Hello! We have Pacemaker cluster of two node Active/Backup (OS Centos 6.7), with resources IPaddr2 and ldirectord. Cluster Properties: cluster-infrastructure: cman dc-version: 1.1.11-97629de no-quorum-policy: ignore stonith-enabled: false The cluster has been configured for this documentation: ht

Re: [ClusterLabs] pcs testsuite status

On Tue, Jun 28, 2016 at 02:35:53PM +0200, Tomas Jelinek wrote: > You are right. The right pacemaker (and corosync, resource agents...) > version is needed for tests to pass. It's not an easy task to figure out > what the right version is, though. For pcs 0.9.152 it's > pacemaker-1.1.15-2.el7. > >

Re: [ClusterLabs] Limiting number of nodes that can join into a cluster

Hmm. That is also a possibility. Thanks Chrissie. On Tue, Jun 28, 2016 at 6:13 PM, Christine Caulfield wrote: > On 28/06/16 13:27, Nikhil Utane wrote: > > Hi Klaus, > > > > I am using multicast to avoid having to configure the host names. > > > > To be honest, if you're serious about keeping the

Re: [ClusterLabs] Limiting number of nodes that can join into a cluster

On 28/06/16 13:27, Nikhil Utane wrote: > Hi Klaus, > > I am using multicast to avoid having to configure the host names. > To be honest, if you're serious about keeping the number of nodes down, then careful management is the way to do it, looking for a technical fix is not the answer. Yes, you

Re: [ClusterLabs] pcs testsuite status

Dne 28.6.2016 v 14:06 Valentin Vidic napsal(a): I'm trying to run pcs tests on Debian unstable, but there are some strange failures like diffs failing due to an additional space at the end of the line or just with "Error: cannot load cluster status, xml does not conform to the schema" Any idea w

Re: [ClusterLabs] Limiting number of nodes that can join into a cluster

Hi Klaus, I am using multicast to avoid having to configure the host names. -Thanks Nikhil On Tue, Jun 28, 2016 at 5:53 PM, Klaus Wenninger wrote: > On 06/28/2016 01:18 PM, Nikhil Utane wrote: > > Hi, > > > > I want to limit the number of nodes that can form a cluster to single > > digit (say

Re: [ClusterLabs] Limiting number of nodes that can join into a cluster

On 06/28/2016 01:18 PM, Nikhil Utane wrote: > Hi, > > I want to limit the number of nodes that can form a cluster to single > digit (say 6). I can do it using application-level logic but would > like to know if there is any option in Corosync that would do it for > me. (Didn't find one). Going unic

[ClusterLabs] pcs testsuite status

I'm trying to run pcs tests on Debian unstable, but there are some strange failures like diffs failing due to an additional space at the end of the line or just with "Error: cannot load cluster status, xml does not conform to the schema" Any idea what could be the issue here? I assume the tests w

[ClusterLabs] Limiting number of nodes that can join into a cluster

Hi, I want to limit the number of nodes that can form a cluster to single digit (say 6). I can do it using application-level logic but would like to know if there is any option in Corosync that would do it for me. (Didn't find one). If there is some #define, can I change it without any side-effect

Re: [ClusterLabs] problems with a CentOS7 SBD cluster

On Tue, Jun 28, 2016 at 11:51 AM, Klaus Wenninger wrote: > On 06/28/2016 11:24 AM, Marcin Dulak wrote: > > > > > > On Tue, Jun 28, 2016 at 5:04 AM, Andrew Beekhof > > wrote: > > > > On Sun, Jun 26, 2016 at 6:05 AM, Marcin Dulak > > mailto:marcin.du...@gmail.co

Re: [ClusterLabs] problems with a CentOS7 SBD cluster

On 06/28/2016 11:24 AM, Marcin Dulak wrote: > > > On Tue, Jun 28, 2016 at 5:04 AM, Andrew Beekhof > wrote: > > On Sun, Jun 26, 2016 at 6:05 AM, Marcin Dulak > mailto:marcin.du...@gmail.com>> wrote: > > Hi, > > > > I'm trying to get familiar with STON

Re: [ClusterLabs] problems with a CentOS7 SBD cluster

On Tue, Jun 28, 2016 at 5:04 AM, Andrew Beekhof wrote: > On Sun, Jun 26, 2016 at 6:05 AM, Marcin Dulak > wrote: > > Hi, > > > > I'm trying to get familiar with STONITH Block Devices (SBD) on a 3-node > > CentOS7 built in VirtualBox. > > The complete setup is available at > > https://github.com/m

Re: [ClusterLabs] eventmachine gem in pcsd

Dne 27.6.2016 v 20:53 Valentin Vidic napsal(a): Hi, Is it safe to drop eventmachine as a dependency? I see it's only mentioned in the makefiles and not used by any of the ruby code: pcsd/Makefile: vendor/cache/eventmachine-1.2.0.1.gem \ pcsd/Gemfile:gem 'eventmachine' pcsd/Gemfile.lock:eve