[Pacemaker] Location issue

[Andrew Beekhof]

On Mon, Jul 11, 2011 at 6:18 AM, ruslan usifov <ruslan.usifov at gmail.com> wrote:
>
>
> 2011/7/5 Andrew Beekhof <andrew at beekhof.net>
>>
>> On Mon, Jul 4, 2011 at 11:42 PM, ruslan usifov <ruslan.usifov at gmail.com>
>> wrote:
>> >
>> >
>> > 2011/6/27 Andrew Beekhof <andrew at beekhof.net>
>> >>
>> >> On Tue, Jun 21, 2011 at 10:22 PM, ruslan usifov
>> >> <ruslan.usifov at gmail.com>
>> >> wrote:
>> >> > No, i mean that in this constaint:
>> >> >
>> >> > location ms_drbd_web-U_slave_on_drbd3 ms_drbd_web-U \
>> >> >         rule role="slave" -inf: #uname ne drbd3
>> >> >
>> >> > pacemaker will try to start slave part of resource (if drbd3 is down)
>> >> > on
>> >> > other nodes, but it doesn't must do that.
>> >>
>> >> The only way to express this is to have:
>> >> - a fake resource that can only run on drbd3, and
>> >> - an ordering constraint tells ms_drbd_web-U to start only after the
>> >> fake resource is active
>> >>
>> >
>> > In future releases does this change?
>>
>> Its a planned but unimplemented feature.
>>
>
> Whether you can roughly tell when this will be fixed?

No idea.