[Pacemaker] Best way to specify colocation and ordering

[Andrew Beekhof]

On Fri, Aug 13, 2010 at 5:43 PM, Dejan Muhamedagic <dejanmm at fastmail.fm> wrote:
> Hi,
>
> On Fri, Aug 13, 2010 at 02:55:30PM +0000, Chris Picton wrote:
>> On Fri, 13 Aug 2010 14:37:18 +0000, Chris Picton wrote:
>>
>> >>> On Fri, Aug 13, 2010 at 01:44:28PM +0000, Chris Picton wrote: I have a
>> >>> drbd backed mysql server which has the following resources:
>> >>>
>> >>> drbd0 -> lvm_data -> mount_data
>> >>> drbd1 -> lvm_logs -> mount_logs
>> >>> mysqld
>> >>> floatingip
>> >>>
>>
>> > Should I need to also specify the demote ordering,
>>
>> This has turned out to be true - I need to specify the order on promote
>> and demote as follows:
>>
>> colocation col_data inf: ms_drbd0:Master group_data group_mysql FloatingIP
>>
>> colocation col_logs inf: ms_drbd1:Master group_logs group_mysql FloatingIP
>>
>> order order_data inf: ms_drbd0:promote group_data:start group_mysql:start
>> FloatingIP:start
>>
>> order order_data_stop inf: FloatingIP:stop group_mysql:stop
>> group_data:stop ms_drbd0:demote
>>
>> order order_logs inf: ms_drbd1:promote group_logs:start group_mysql:start
>> FloatingIP:start
>
> You can also try to add symmetrical=true, though that should be
> default.
>
>> order order_logs_stop inf: FloatingIP:stop group_mysql:stop
>> group_logs:stop ms_drbd1:demote
>>
>> It seems a but long-winded, but does work
>
> I find it odd that the chain of two-resource constraints didn't
> work.

Especially since thats what the set expands to.