[Pacemaker] group resource - altering default order

Andrew Beekhof andrew at beekhof.net
Fri Jun 15 00:34:45 EDT 2012


On Fri, Jun 15, 2012 at 11:06 AM, David Coulson <david at davidcoulson.net> wrote:
>
> On 6/14/12 8:28 PM, Andrew Beekhof wrote:
>>
>> Just use a colocation set instead.
>
> Is there a better option than a non-ordered,non-collocated group when you
> need a order dependency?

Try an ordering set :-)
http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-resource-sets-ordering.html

> We have a couple of clone resources, which are
> dependent on a non-collocated group (the resources in the group are
> distributed across the nodes in the cluster). Seems to work pretty well,
> although I have to 'crm resource restart gr-whatever' when we reboot a node
> to get it to redistribute everything again - I think that is because I have
> my default stickiness set to 200.
>
> I realize you hate non-ordered,non-collocated groups, but they are
> occasionally useful as a resource container :)
>
> David
>




More information about the Pacemaker mailing list