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
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 react...and there's really no way
On Sun, 2018-05-13 at 22:58 +0800, Confidential Company wrote:
> Hi Casey,
>
> 1. I tried shutting down my VM while testing, the "ClusterIP"
> resource switched automatically onto the standy node(Node2)
> 2. I do "systemctl enable corosnyc/pacemaker" - so that after reboot,
> corosync and pacemake
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
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 Vi
