--- On Wed, 12/3/08, Andrew Beekhof <[EMAIL PROTECTED]> wrote:
> From: Andrew Beekhof <[EMAIL PROTECTED]>
> Subject: Re: [Linux-HA] Re: Active Ressources should be always on the same
> node
> To: "General Linux-HA mailing list" <[email protected]>
> Date: Wednesday, December 3, 2008, 3:40 PM
> On Wed, Dec 3, 2008 at 18:47, Thomas Mueller
> <[EMAIL PROTECTED]> wrote:
> >
> >>> <resources>
> >>> <primitive
> id="ip_resource_1" class="ocf"
> type="IPaddr"
> >>> provider="heartbeat">
> >>> <instance_attributes
> id="inst_attr">
> >>> <attributes>
> >>> <nvpair name="ip"
> value="@VIRTUAL_IP@" id="vip1"/>
> >>> </attributes>
> >>> </instance_attributes>
> >>> </primitive>
> >>> <primitive id="myscript"
> class="heartbeat"
> >>> type="myscript-haswitch"
> provider="heartbeat"/>
> >>> </resources>
> >>>
> >>> so when i just put <group
> id="some_id"> around these primitives, it
> >>> should work out of the box? Both ressources
> will only always run on the
> >>> same node, if that node goes offline another
> node will manage both
> >>> ressources again?
> >>
> >> Yes.
> >>
> >> Groups are colocated and ordered by default. That
> means the cluster
> >> decides where the group should run and then starts
> the resources one
> >> after another on that node.
> >
> >
> > is possible to tell the group that it's not
> ordered but only colocated?
>
> yes, but please don't :-)
>
> > just out of curiosity - haven't found any
> reference on how to do this.
sorry, in this context - what does ordered refer to? That all primitives in a
group are started in that order?
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
