[Linux-HA] Colocation of promoted DRBD resources

[Remigiusz Stachura]

I have created colocation:
<rsc_colocation id="drbd0_drbd1_master" from="ms-drbd0"
from_role="master" to="ms-drbd1" to_role="master" score="INFINITY"/>
but after putting it to cib.xml I get stange effect - resource
ms-drbd0 on node2 stop running:
node1: ms-drbd0 - master, ms-drbd1 - master
node2: ms-drbd0 - not running, ms-drbd1 - slave.
After removing the colocation everything works like befor.

What are another ways? Is it possible by using scores to make change
of state of one resource to have effect to another ones?

thanks

2007/10/31, Andrew Beekhof <beekhof at gmail.com>:
> On 10/29/07, Remigiusz Stachura <remigiusz.stachura at gmail.com> wrote:
> > Hi,
> > I have a two-node cluster that has more then 2 multi-state drbd
> > resources on each node. All these resources must be promoted
> > to master state on the same node because they creates a filesystem for
> > Xen DomU. Xen will never migrate so I use DRBD 7.x and the most fresh
> > HA 2.1.2-15 working on SLES10 SP1.
> > I have created configuration included as a cib2.xml which mainly do what I want.
> > (for testing only there are 2 drbd resources and IPaddr resource - not
> > Xen resource)
> >
> > My problem is I wasn't able to create rule which make:
> >
> > -if one of the drbd resources fail on the primary node, all of them
> > should be on the secondary node promoted to master before starting
> > there Xen.
>
> did you try a colocation constraint with from_role and to_role both
> set to Master?
>
> >
> > How can I create such rules?
> > Could you give same examples?
> >
> > thanks in advance
> >
> > _______________________________________________
> > Linux-HA mailing list
> > Linux-HA at lists.linux-ha.org
> > http://lists.linux-ha.org/mailman/listinfo/linux-ha
> > See also: http://linux-ha.org/ReportingProblems
> >
> >
> _______________________________________________
> Linux-HA mailing list
> Linux-HA at lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>