[ClusterLabs] R: Re: Ordering Sets of Resources

Ken Gaillot kgaillot at redhat.com
Mon Feb 27 13:16:55 EST 2017

On 02/26/2017 02:45 PM, ivagal at libero.it wrote:
> Hi,
> yes, I want, with active resources, that I can turn them off individually.
> With symmetrical=true when i stop a resource, for example MYIP_4, also MYSMTP 
> will stop.
> Ragards
> Ivan

I thought that was the goal, to ensure that things are stopped in order.

If your goal is to start and stop them in order *if* they're both
starting or stopping, but not *require* it, then you want kind=Optional
instead of Mandatory.

>> ----Messaggio originale----
>> Da: "Ken Gaillot" <kgaillot at redhat.com>
>> Data: 26/02/2017 20.04
>> A: <users at clusterlabs.org>
>> Ogg: Re: [ClusterLabs] Ordering Sets of Resources
>> On 02/25/2017 03:35 PM, ivagal at libero.it wrote:
>>> Hi all,
>>> i have configured a two node cluster on redhat 7.
>>> Because I need to manage resources stopping and starting singularly when
>>> they are running I have configured cluster using order set constraints.
>>> Here the example
>>> Ordering Constraints:
>>>   Resource Sets:
>>>     set MYIP_1 MYIP_2 MYFTP MYIP_5 action=start sequential=false
>>> require-all=true set MYIP_3 MYIP_4 MYSMTP action=start sequential=true
>>> require-all=true setoptions symmetrical=false
>>>     set MYSMTP MYIP_4 MYIP_3 action=stop sequential=true
>>> require-all=true set MYIP_5 MYFTP MYIP_2 MYIP_1 action=stop
>>> sequential=true require-all=true setoptions symmetrical=false 
> kind=Mandatory
>>> The constrait work as expected on start but when stopping the resource
>>> don't respect the order.
>>> Any help is appreciated
>>> Thank and regards
>>> Ivan
>> symmetrical=false means the order only applies for starting

More information about the Users mailing list