[Pacemaker] Colocation set options (pcs syntax)

Asgaroth lists at blueface.com
Fri Feb 28 03:32:32 EST 2014

> pcs constraint colocation set fs_ldap-clone sftp01-vip ldap1 
> sequential=true
> Let me know if this does or doesn't work for you.

I have been testing this now for a couple days and I think I must be 
doing something wrong, firstly though, the command itself completes 

# pcs constraint show --full
   Resource Sets:
     set fs_ldap-clone sftp01-vip ldap1 sequential=true (id:pcs_rsc_set) 

However, if I try to test it by moving, for example, the "sftp01-vip" 
resource group to another node, then is does not move the ldap1 service 
with it, example below:

Cluster state before resource move:

Then I do "pcs resource move sftp01-vip bfievsftp02", which moves 
resources to the node (except the associated ldap1 service)

Cluster state after the move:

Full constraint list:

Here is what I am trying to achieve:
[1] The sftp0[1-3]-vip groups each have a prefered node 
(sftp01-vip=node1, sftp02-vip=node2, sftp03-vip=node3
[2] The sftp0[1-3] lsb resources are colocated with sftp0[1-3]-vip groups
[3] The ldap[1-3] lsb resources are colocated with sftp0[1-3]-vip groups

I managed to achieve the above using logic contraints as listed in the 
constraint output, however, the sftp0[1-3] and ldap[1-3] lsb resources 
also depend on fs_cdr-clone and fs_ldap-clone respectively, being available.

I thought I would be able to achive that file system dependancy using 
the colocation set, but this does not seem to work the way I am 
expecting it to, or, quite possibly, my logic may be slightly(largely) 
off :)

How would I ensure, that in the case of a node failure, the vip group 
moves to a node which has the fs_cdr and fs_ldap file system resources 
available? If I can do that, then, I can keep the colocation rule for 
the sftp/ldap service with the vip group. Or am I thinking about this 
the wrong way around?

Any tips/suggestions would be appreciated.


More information about the Pacemaker mailing list