>>
>> pcs constraint order start main1 then stop backup1 kind=Serialize
>
> I think you want kind=Optional here. "Optional" means that if both
> actions are needed in the same transition, perform them in this order,
> otherwise it doesn't limit anything. "Serialize" means the start and
> stop
On Fri, 2017-09-08 at 15:31 +1000, Leon Steffens wrote:
> Hi all,
>
> We are running Pacemaker 1.1.15 under Centos 6.9, and have a simple
> 3-node cluster with 6 sets of "main" and "backup" resources (just
> Dummy ones):
>
> main1
> backup1
> main2
> backup2
> etc.
>
> We have the following
Hi all,
We are running Pacemaker 1.1.15 under Centos 6.9, and have a simple 3-node
cluster with 6 sets of "main" and "backup" resources (just Dummy ones):
main1
backup1
main2
backup2
etc.
We have the following co-location constraint between main1 and backup1
(-200 because we don't want them to
