[Pacemaker] Active / Active pacemaker configuration advice

Marko Potocnik marko.potocnik at gmail.com
Thu Nov 25 02:56:21 EST 2010


On Wed, Nov 24, 2010 at 4:04 PM, Michael Schwartzkopff <misch at clusterbau.com
> wrote:

> On Tuesday 23 November 2010 10:21:04 Marko Potocnik wrote:
> > On Tue, Nov 23, 2010 at 9:55 AM, Michael Schwartzkopff
> > <misch at clusterbau.com
> >
> > > wrote:
> > >
> > > On Tuesday 23 November 2010 09:10:58 Marko Potocnik wrote:
> > > > Hi,
> > > >
> > > >
> > > >
> > > > I am trying to configure a service (ftp for proof of concept) to run
> in
> > >
> > > an
> > >
> > > > active / active configuration. A floating IP is used to access this
> > > > service. What I am trying to achieve is that a floating IP would move
> > > > to second node, if service fails on the first node. After that
> service
> > >
> > > should
> > >
> > > > be restarted.
> > > >
> > > > I am able to achieve all but the restart of the service with the
> > >
> > > following
> > >
> > > > configuration:
> > > >
> > > >
> > > >
> > > > node $id="34d5eba9-130f-4c64-9460-4a5310ac510c" jesenice.iskratel.si\
> > > >
> > > >         attributes standby="off"
> > > >
> > > > node $id="5fdf23a5-61c4-4a57-80fb-c764954a5f14" olimpija.iskratel.si\
> > > >
> > > >         attributes standby="off"
> > > >
> > > > *primitive res_ftp lsb:vsftpd \*
> > > >
> > > > *        meta migration-threshold="1" \*
> > > >
> > > > *        op monitor on-fail="restart" interval="10s"*
> > > >
> > > > *primitive res_ip_ftp ocf:heartbeat:IPaddr2 \*
> > > >
> > > > *        params ip="172.18.251.6" cidr_netmask="24" \*
> > > >
> > > > *        op monitor interval="15s" timeout="30s"*
> > > >
> > > > *clone c_ftp res_ftp \*
> > > >
> > > > *        meta clone-max="2" clone-node-max="1"
> globally-unique="false"
> > > > target-role="Started"*
> > > >
> > > > *colocation c_ip_on_ftp inf: res_ip_ftp c_ftp*
>
> Here I'm am missing I'd like to see something like
>
> order ord_FTP_IP inf: c_ftp res_ip_ftp
>
>
The order constraint does not affect the IP migration strategy in case of
service failure. I agree that I missed it, but I does not affect the current
behavior of IP resource in case of service failure.


>
> --
> Dr. Michael Schwartzkopff
> Guardinistr. 63
> 81375 München
>
> Tel: (0163) 172 50 98
>
> _______________________________________________
> 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/20101125/194294de/attachment-0001.html>


More information about the Pacemaker mailing list