[Pacemaker] Location issue

[ruslan usifov]

In this configuration ms_drbd_web-U is stacked resource(for backup purposes)
and it slave part must run only on dedicated host (can't migrate to other)

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
>
> Seems like a strange setup for drbd though.  Are you sure you
> understand how its supposed to work?
>
> > For example on follow
> > configuration:
> >
> > location ms_drbd_svn_slave_on_backup0 ms_drbd_svn-U \
> >         rule role="Slave" -inf: #uname ne backup0
> >
> >
> > I see follow in failed actions:
> >
> >  drbd_svn-U:1_start_0 (node=storage1, call=364, rc=-2, status=Timed Out):
> > unknown exec error.
> >
> >
> > But as i think pacemaker doesn't must try do start actions on Slave part
> of
> > resource ms_drbd_svn-U on node storage1. And this looks like bug or
> perhaps
> > i misunderstand some things.
> >
> > 2011/6/21 Andrew Beekhof <andrew at beekhof.net>
> >>
> >> On Fri, Jun 17, 2011 at 9:31 AM, ruslan usifov <ruslan.usifov at gmail.com
> >
> >> wrote:
> >> > Andrew does any chance to fix this behaivour??? Now this constraint
> >> > doesn't
> >> > work:
> >>
> >> Define "doesn't work"?
> >> Not accepted by the shell?  Allow's it to be started elsewhere?
> >> In the later case, please include a crm_report covering the time when
> >> ms_drbd_web-U was promoted in the incorrect location
> >>
> >> >
> >> > location ms_drbd_web_slave_on_backup0 ms_drbd_web-U \
> >> >         rule $id="ms_drbd_web_slave_on_backup0-rule" $role="Slave"
> -inf:
> >> > #uname ne backup0
> >> >
> >> >
> >> > 2011/6/8 ruslan usifov <ruslan.usifov at gmail.com>
> >> >>
> >> >> I want exactly slave role will be launch only drbd3 (stacked drbd
> >> >> resource). So disable launch resource on drbd3 at all not good
> solution
> >> >> for
> >> >> me
> >> >>
> >> >> 2011/6/8 Dominik Klein <dk at in-telegence.net>
> >> >>>
> >> >>> Try without role. If the resource must not run on the node at all,
> >> >>> then
> >> >>> the role does not matter. Maybe there's a bug with role="slave"?
> >> >>>
> >> >>> On 06/08/2011 10:56 AM, ruslan usifov wrote:
> >> >>> > i try follow:
> >> >>> >
> >> >>> > location ms_drbd_web-U_slave_on_drbd3 ms_drbd_web-U \
> >> >>> >         rule role="slave" -inf: #uname ne drbd3
> >> >>> >
> >> >>> > result is identical, pacemaker try launch slave role on other
> >> >>> > nodes:-(((
> >> >>> >
> >> >>> >
> >> >>> > 2011/6/8 Dominik Klein <dk at in-telegence.net
> >> >>> > <mailto:dk at in-telegence.net>>
> >> >>> >
> >> >>> >     >> but when i shutdown drbd3 host Pacemaker try start slave
> role
> >> >>> > on
> >> >>> >     >> other host. How can i prevent this behavior?
> >> >>> >     >
> >> >>> >     > try
> >> >>> >     > s/inf/-inf
> >> >>> >     > s/eq/neq
> >> >>> >
> >> >>> >     "ne" actually, sorry
> >> >>>
> >> >>> _______________________________________________
> >> >>> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> >> >>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> >> >>>
> >> >>> Project Home: http://www.clusterlabs.org
> >> >>> Getting started:
> >> >>> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> >> >>> Bugs:
> >> >>>
> >> >>>
> http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
> >> >>
> >> >
> >> >
> >> > _______________________________________________
> >> > Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> >> > http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> >> >
> >> > Project Home: http://www.clusterlabs.org
> >> > Getting started:
> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> >> > Bugs:
> >> >
> >> >
> http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
> >> >
> >> >
> >>
> >> _______________________________________________
> >> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> >> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> >>
> >> Project Home: http://www.clusterlabs.org
> >> Getting started:
> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> >> Bugs:
> >>
> http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
> >
> >
> > _______________________________________________
> > Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> > http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> >
> > Project Home: http://www.clusterlabs.org
> > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> > Bugs:
> >
> http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
> >
> >
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs:
> http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20110627/ea2cbd2a/attachment.htm>