$cat /etc/redhat-release
CentOS release 6.4 (Final)
$rpm -qa | grep -i pcs
pcs-0.9.26-10.el6_4.1.noarch
So look like I might have an older version of pcs ..
--
!!!!!
( o o )
--------------oOO----(_)----OOo--------------
Luc Paulin
email: paulinster(at)gmail.com
Skype: paulinster
2014/1/2 Chris Feist <cfe...@redhat.com>
> On 01/02/2014 01:54 PM, Luc Paulin wrote:
>
>> Thanx for the syntax, however it does not seem to work.
>> When I try it, it immediately return the help syntax menu, as if the
>> command not
>> suported.
>>
>> [root@fwcorp-01 (NEW FW HOST) ~]$pcs constraint colocation set
>> vip_v253_178
>> vip_v253_179 vip_v253
>>
>
> Which version of pcs are you using? (colocation sets were included in
> 0.9.62)
>
>
>> Usage: pcs constraint [constraints]...
>> Manage resource constraints
>>
>> Commands:
>> [...cut...]
>>
>>
>> The only possible syntax look to be:
>> pcs constraint colocation [show [all]]
>> pcs constraint colocation add <source resource> <target resource> [score]
>> [options]
>> pcs constraint colocation rm <source resource> <target resource>
>>
>> I found the following link that refer to the constraint colocation set
>> (http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html/
>> Pacemaker_Explained/s-resource-sets-collocation.html)
>> however there's no reference to the pcs command
>>
>>
>>
>>
>>
>> --
>> !!!!!
>> ( o o )
>> --------------oOO----(_)----OOo--------------
>> Luc Paulin
>> email: paulinster(at)gmail.com <http://gmail.com>
>> Skype: paulinster
>>
>>
>>
>> 2014/1/2 Chris Feist <cfe...@redhat.com <mailto:cfe...@redhat.com>>
>>
>>
>> On 01/02/2014 10:37 AM, Lars Marowsky-Bree wrote:
>>
>> On 2014-01-02T11:22:01, Luc Paulin <paulins...@gmail.com
>> <mailto:paulins...@gmail.com>> wrote:
>>
>> That make sense to use the colocation. So I guess that I
>> should define a
>> "master" resource and tell each other resource that they
>> should
>> colocated
>> on the same node at the "master" resource.
>>
>>
>> You could also use a resource set to achieve this, but I don't
>> know the
>> pcs syntax for it.
>>
>>
>> You can create a resource set with pcs like this:
>> pcs constraint colocation set resourceA resourceB ...
>>
>> Thanks!
>> Chris
>>
>>
>>
>> Regards,
>> Lars
>>
>>
>>
>> _________________________________________________
>> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
>> <mailto:Pacemaker@oss.clusterlabs.org>
>> http://oss.clusterlabs.org/__mailman/listinfo/pacemaker
>>
>> <http://oss.clusterlabs.org/mailman/listinfo/pacemaker>
>>
>> Project Home: http://www.clusterlabs.org
>> Getting started: http://www.clusterlabs.org/__
>> doc/Cluster_from_Scratch.pdf
>>
>> <http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf>
>> Bugs: http://bugs.clusterlabs.org
>>
>>
>>
>>
>> _______________________________________________
>> Pacemaker mailing list: Pacemaker@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
>>
>>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker@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
>
_______________________________________________
Pacemaker mailing list: Pacemaker@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
