[Pacemaker] Dependency on either of two resources

[Vladislav Bogdanov]

Hi all,

just wondering, is there a way to make resource depend on (be colocated
with) either of two other resources?

Use case is iSCSI initiator connection to iSCSI target with two portals.
Idea is to have f.e. device manager multipath resource depend on both
iSCSI connection resources, but in a "soft" way, so fail of any single
iSCSI connection will not cause multipath resource to stop, but fail of
both connections will cause it.

I should be missing something but I cannot find answer is it possible
with current pacemaker. Can someone bring some light?

Best,
Vladislav

___
Pacemaker mailing list: Pacemaker@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

Re: [Pacemaker] promote a ms resource to a node

[Pavlos Parissis]

just for the record here is the constraint
location master-location ms-drbd_02 \
rule $id="master-rule" $role="Master" 1000: #uname eq node-03
Cheers,
Pavlos


On 30 September 2010 10:24, Andrew Beekhof  wrote:

> A resource location constraint with role=Master would do it.
> Not sure about the shell syntax though.
>
> On Tue, Sep 28, 2010 at 3:51 PM, Pavlos Parissis
>  wrote:
> > Hi,
> >
> > Let's say that I have manually demote a ms resource and have the
> following
> > situation
> > crm(live)resource# demote ms-drbd_01
> > crm(live)resource# status
> > [..snip..]
> > Master/Slave Set: ms-drbd_01
> >  Slaves: [ node-01 node-03 ]
> >
> > How can I manually promote ms-drbd_01 on node-03?
> > The promote command doesn't accept node names and the move command on
> > ms-drbd_01 says can't find resource.
> >
> > Cheers,
> > Pavlos
> >
> >
> > ___
> > Pacemaker mailing list: Pacemaker@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@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@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] Fail over algorithm used by Pacemaker

[hudan studiawan]

Hi,

I want to start to contribute to Pacemaker project. I start to read
Documentation and try some basic configurations. I have a question: what
kind of algorithm used by Pacemaker to choose another node when a node die
in a cluster? Is there any manual or documentation I can read?

Thank you,
Hudan
___
Pacemaker mailing list: Pacemaker@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