[Pacemaker] Looking for correct constraints

Andrew Beekhof andrew at beekhof.net
Fri Oct 30 18:04:53 EDT 2009


On Fri, Oct 30, 2009 at 7:06 PM, Lars Marowsky-Bree <lmb at suse.de> wrote:
> On 2009-10-30T16:41:34, Andrew Beekhof <andrew at beekhof.net> wrote:
>
>> >> This does not make any sense. Sorry, let me try again.
>> >>
>> >> res1 start = set attribute
>> >> res1 stop = delete attribute
>> >>
>> >> rule for res2 with -inf score if attribute is set.
>> >
>> > better, just give all your nodes an attribute with the same value and
>> > use a colocation constraint with a score-attribute (IIRC)
>>
>> sorry, s/score-attribute/node-attribute/
>
> The problem with this obviously is that the attribute is not removed if
> res1 has been fenced.

Whats that matter?

The point is that node-attribute=xyz performs (anti-)colocation based
on attribute "xyz" _instead_ of the implied #uname.




More information about the Pacemaker mailing list