Re: [ClusterLabs] Configuring booth for multi-site cluster

Le mardi 31 octobre 2017 à 08:25 +0100, Dejan Muhamedagic a écrit : > * is it a good idea to route the booth plain UDP/9929 traffic via > > Internet ? (the firewalls are configured to accept only traffic > > from/to > > the known public addresses, and the booth shared secret > > authentication > >

Re: [ClusterLabs] Pacemaker resource parameter reload confusion

On Tue, 2017-10-31 at 18:44 +0100, Ferenc Wágner wrote: > Ken Gaillot writes: > > > The pe-input is indeed entirely sufficient. > > > > I forgot to check why the reload was not possible in this case. It > > turns out it is this: > > > >    trace: check_action_definition:   

Re: [ClusterLabs] Pacemaker resource parameter reload confusion

Ken Gaillot writes: > The pe-input is indeed entirely sufficient. > > I forgot to check why the reload was not possible in this case. It > turns out it is this: > >    trace: check_action_definition:  Resource vm-alder doesn't know > how to reload > > Does the resource

Re: [ClusterLabs] 'expected' node attribute missing

On Mon, 2017-10-30 at 10:48 +0600, Sergey Korobitsin wrote: > Ken Gaillot ☫ → To Cluster Labs - All topics related to open-source > clustering welcomed @ Fri, Oct 27, 2017 10:38 -0500 > > > > Hello, > > > I'm trying to use https://github.com/marcan/pacemaker-exporter, > > > and it wants

Re: [ClusterLabs] Pacemaker resource parameter reload confusion

On Tue, 2017-10-31 at 09:33 +0100, Ferenc Wágner wrote: > Ken Gaillot writes: > > > On Fri, 2017-10-20 at 15:52 +0200, Ferenc Wágner wrote: > > > > > Ken Gaillot writes: > > > > > > > On Fri, 2017-09-22 at 18:30 +0200, Ferenc Wágner wrote: > > > > >

Re: [ClusterLabs] Colocation rule with vip and ms master

On Mon, 2017-10-30 at 16:46 +, Norberto Lopes wrote: > Apologies but I'm not following. I'm probably misunderstanding > something. > > From what I could gather from https://clusterlabs.org/doc/en-US/Pacem > aker/1.1/html/Pacemaker_Explained/_mandatory_placement.html I can't > follow the

Re: [ClusterLabs] different start/stop order

On Fri, 2017-10-27 at 22:08 +0200, Stefan Krueger wrote: > Hello Ken, thanks for this information! > > > You can make ordering constraints asymmetrical, > > so they only apply in the listed direction: > > > > http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html-single/Pace > >

Re: [ClusterLabs] How to mount rpc_pipefs on a different mountpoint on RHEL/CentOS 7?

Dennis Jacobfeuerborn writes: > if I create a new unit file for the new file the services would not > depend on it so it wouldn't get automatically mounted when they start. Put the new unit file under /etc/systemd/system/x.service.requires to have x.service require it. I

[ClusterLabs] How to mount rpc_pipefs on a different mountpoint on RHEL/CentOS 7?

Hi, I'm trying to create a redundant NFS system but hit a problem with the way the nfs packages on RHEL/CentOS 7 handle the sunrpc mount point. I put /var/lib/nfs on its own redudant drbd device but on a failover the nfsserver resource agent complains that something is already mounted below

Re: [ClusterLabs] corosync race condition when node leaves immediately after joining

Jonathan, Hi Honza, On 19/10/17 17:05, Jonathan Davies wrote: On 19/10/17 16:56, Jan Friesse wrote: Jonathan, On 18/10/17 16:18, Jan Friesse wrote: Jonathan, On 18/10/17 14:38, Jan Friesse wrote: Can you please try to remove "votequorum_exec_send_nodeinfo(us->node_id);" line from

Re: [ClusterLabs] corosync race condition when node leaves immediately after joining

Hi Honza, On 19/10/17 17:05, Jonathan Davies wrote: On 19/10/17 16:56, Jan Friesse wrote: Jonathan, On 18/10/17 16:18, Jan Friesse wrote: Jonathan, On 18/10/17 14:38, Jan Friesse wrote: Can you please try to remove "votequorum_exec_send_nodeinfo(us->node_id);" line from votequorum.c

Re: [ClusterLabs] Pacemaker resource parameter reload confusion

Ken Gaillot writes: > On Fri, 2017-10-20 at 15:52 +0200, Ferenc Wágner wrote: > >> Ken Gaillot writes: >> >>> On Fri, 2017-09-22 at 18:30 +0200, Ferenc Wágner wrote: >>> Ken Gaillot writes: > Hmm, stop+reload is

Re: [ClusterLabs] Configuring booth for multi-site cluster

Hi, On Mon, Oct 30, 2017 at 07:03:28PM +0100, Nicolas Huillard wrote: > Hello all, > > I have 2 sites, each with an independent configured cluster > (corosync+pacemaker), and an arbitrator server, which is behind a NAT > connection to the Internet. > I see in the booth.conf templates that each

Re: [ClusterLabs] Colocation rule with vip and ms master

Norberto Lopes writes: > On Fri, 27 Oct 2017 at 06:41 Ferenc Wágner wrote: > >> Norberto Lopes writes: >> >>> colocation backup-vip-not-with-master -inf: backupVIP postgresMS:Master >>> colocation backup-vip-not-with-master inf:

Re: [ClusterLabs] Colocation rule with vip and ms master

Apologies but I'm not following. I'm probably misunderstanding something. >From what I could gather from https://clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/_mandatory_placement.html I can't follow the subtle difference between the two on a running cluster. As an example: If

[ClusterLabs] Configuring booth for multi-site cluster

Hello all, I have 2 sites, each with an independent configured cluster (corosync+pacemaker), and an arbitrator server, which is behind a NAT connection to the Internet. I see in the booth.conf templates that each site/arbitrator is only designated by a single IP address, not taking into account