[Pacemaker] Pacemaker 1.1.7 order constraint syntax

[Rasto Levrinc]

On Thu, Jul 19, 2012 at 2:38 PM, Andreas Kurz <andreas at hastexo.com> wrote:
> On 07/19/2012 11:47 AM, Vadym Chepkov wrote:
>> Hi,
>>
>> When Pacemaker 1.1.7 was announced, a new feature was mentioned:
>>
>> The ability to specify that A starts after ( B or C or D )
>>
>> I wasn't able to find an example how to express it crm shell in neither man crm nor in Pacemaker Explained.
>> In fact, http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-resource-ordering.html doesn't have new attribute listed either.
>> Is it supported in crm ?
>
> I don't think it is supported in crm or any other configuration tool
> .... syntax for above example in xml looks like:

Well, LCMC supports this, btw last time I checked this feature
is still not enabled in constrains rng in 1.1.7 by default, so you
have to wait at least for 1.1.8, or enable it yourself.
It also doesn't work if combined with colocation.

Rasto

>
> <rsc_order id="order-1">
>       <resource_set id="req-1" sequential="false" require-all="false">
>         <resource_ref id="B"/>
>         <resource_ref id="C"/>
>         <resource_ref id="D"/>
>       </resource_set>
>       <resource_set id="req-2">
>         <resource_ref id="A"/>
>       </resource_set>
> </rsc_order>
>
> ... can be found in the pengine regression tests directory in Pacemaker
> source ...

-- 
Dipl.-Ing. Rastislav Levrinc
rasto.levrinc at gmail.com
Linux Cluster Management Console
http://lcmc.sf.net/