[Pacemaker] Colocation set options (pcs syntax)

[Chris Feist]

On 02/24/2014 08:28 AM, Asgaroth wrote:
> Hi All,
>
> I have several resources that depend on a cloned share file system and vip
> that need to be up and operational before the resource can start, I was
> reading the pacemaker documentation and it looks like colocation sets is
> what I am after. I can see in the documentation that you can define a
> colocation set and set the sequential option to "true" if you need the
> resources to start sequentially, I guess this then becomes an ordered
> colocation set which is what I am after, documentation I was reading is
> here:
>
> http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-re
> source-sets-collocation.html
>
> According to the pcs man page I can setup a colocation set as follows:
>
>      colocation set <resource1> <resource2> [resourceN]... [setoptions] ...
>                 [set <resourceX> <resourceY> ...] [setoptions
> <name>=<value>...]
>
> However when I run the following command to create the set:
>
> pcs constraint colocation set fs_ldap-clone sftp01-vip ldap1 setoptions
> sequential=true

I think there's an error in the man page (which I'll work on getting fixed). 
Can you try: (removing 'setoptions' from your command)


pcs constraint colocation set fs_ldap-clone sftp01-vip ldap1 sequential=true


Let me know if this does or doesn't work for you.

Thanks,
Chris

> I get an error stating:
>
> Error: Unable to update cib
> Call cib_replace failed (-203): Update does not conform to the configured
> schema
>
> And then a dump of the current running info base.
>
> Am I reading the man page incorrectly, or is this a bug I need to report?
>
> Thanks
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>