On 06/14/2017 11:52 AM, Jeff Johnson wrote: > If I have a resource group: > > # pcs resource show > Resource Group: nfs-zfs > nfsnet(ocf::heartbeat:IPaddr2):Started server-a-hb.internal > nfs-daemon(ocf::heartbeat:nfsserver):Started server-a-hb.internal > samba(systemd:smb):Started server-a-hb.internal > netbios(systemd:nmb):Started server-a-hb.internal > nfspool(ocf::heartbeat:ZFS):Started server-a-hb.internal > > > and I create a constraint order set: > > `pcs constraint order set virtip nfssvr samba netbios nfspool` > > > does that order set inherit any enforcement of colocation as well? > > If not, how does colocation get applied to a resource group with ordered > start/stop? Does the resource grouping or order set include some default > enforcement of colocation? > > Thanks, > > --Jeff
Groups imply both colocation and ordering, in the order they appear in the group. In your example above, nfsnet will be started first, then nfs-daemon, etc., all on the same node. Ordering constraints (whether simple or using sets) do not imply colocation. In your example above, virtip and nfssvr must start before samba, but they don't have to be on the same node. _______________________________________________ Users mailing list: [email protected] http://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
