[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-ha
Subject:    Re: [Linux-HA] Problem with creating constraints
From:       Andrew Beekhof <andrew () beekhof ! net>
Date:       2011-09-25 23:55:26
Message-ID: CAEDLWG2EqL_KRSoOtPtrS=GVsgf_x-nGRGmSkg4LZfatvs2UXA () mail ! gmail ! com
[Download RAW message or body]

On Fri, Sep 23, 2011 at 11:00 PM, Lars Ellenberg
<lars.ellenberg@linbit.com> wrote:
> On Fri, Sep 23, 2011 at 12:39:13PM +1000, Andrew Beekhof wrote:
>> On Wed, Sep 21, 2011 at 7:15 PM, Uwe Weiss <u.weiss@netz-objekte.de> wrote:
>> > Hello List,
>> >
>> >
>> >
>> > I have a problem in creating a constraint. I hope that someone could help me
>> > and give me a hint.
>> >
>> >
>> >
>> > I have three resources (A,B,C) and two cluster nodes (node0,node1). Resource
>> > A can run only on node0 and resource B can run only node1.
>> >
>> > I managed this by resource-stickiness INFINITY for each resource.
>>
>> Better to do it the other way, set -INFINITY for the nodes it can't run on.
>>
>> >
>> >
>> >
>> > Resource C can run on both nodes but  on node0 only if resource A is up and
>> > running or on node 1 if resource B is up and running.
>> >
>> > Additionally resource C can only start after resource A or B
>>
>> Currently its not possible to express order {A or B} then C
>
> You could work around that by setting a node attribute (with lifetime
> reboot?) from a sucessful start/monitor, clearing that node attribute on
> stop or failed monitor (of A and B), and using a location constraint
> that requires that attribute for C.

Good thinking, that would certainly work.
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

[prev in list] [next in list] [prev in thread] [next in thread]