[ClusterLabs] How to change the "pcs constraint colocation set"

Hi, We have two VIP resources and we use the following command to make them in different node. pcs constraint colocation set pgsql-slave-ip1 pgsql-slave-ip2 setoptions score=-1000 Now we add a new node into the cluster and we add a new VIP too. We want the constraint colocation set to change

Re: [ClusterLabs] Frequent PAF log messages - Forbidding promotion on in state "startup"

On Mon, 14 May 2018 16:43:52 + "Shobe, Casey" wrote: > Thanks, I should have seen that. I just assumed that everything was working > fine because `pcs status` shows no errors. We do not trigger error for such scenario because it would require the cluster to

Re: [ClusterLabs] Two-node cluster fencing

On Sat, 2018-05-12 at 12:51 -0600, Casey & Gina Shobe wrote: > Without fencing, if the primary is powered off abruptly (e.g. if one > of your ESX servers crashes), the standby will not become primary, > and you will need to promote it manually.  We had exactly this > scenario happen last week with

Re: [ClusterLabs] Ansible role to install corosync and pacemaker

On Fri, 2018-05-11 at 10:51 +, Singh, Niraj wrote: > Hi Team, >   > I am working on masakari/masakari-monitors ansible role. > Ref: https://github.com/openstack/masakari  //project > Ref: https://github.com/openstack/openstack-ansible-os_masakari > //role(developing) >   > “Masakari provides

[ClusterLabs] Antw: Re: Antw: stonith continues to reboot server once fencing occurs

Hi! I'm wondering about this: vmhost1-fsl.bcn is shutting down That doesn't read like a STONITH, but like a regular shutdown (which may hang). The other thing that reads strange for a two-node cluster is this: [11130] vmhost0-fsl.jsc.nasa.gov corosyncnotice [TOTEM ] A new membership