[Pacemaker] Active / Active pacemaker configuration advice

[Marko Potocnik]

On Wed, Nov 24, 2010 at 2:37 PM, Dejan Muhamedagic <dejanmm at fastmail.fm>wrote:

> Hi,
>
> On Tue, Nov 23, 2010 at 09:10:58AM +0100, 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:
>
> You want some kind of hot-standby service? Why would you want to
> restart it then?
>
>
Yes, I want a hot-standby service, so that the failover time is as low as
possible (just move the IP).
I would like to restart it so that the automatic failback is possible.


> > 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*
> >
> > property $id="cib-bootstrap-options" \
> >
> >         dc-version="1.0.8-9881a7350d6182bae9e8e557cf20a3cc5dac3ee7" \
> >
> >         cluster-infrastructure="Heartbeat" \
> >
> >         stonith-enabled="false" \
> >
> >         default-resource-stickiness="200" \
> >
> >         no-quorum-policy="ignore" \
> >
> >         last-lrm-refresh="1290440895"
> >
> >
> >
> > If I up the migration-threshold then service restarts n times, but
> floating
> > IP doesn’t move to another node. Do you have any idea how to achieve the
> > desired configuration?
>
> Sorry, didn't quite understand what you want to achieve. Can you
> please rephrase.
>

I would like the IP to move and ftp service to restart in case of service
failure. But I can only get IP to move and service stays stoped.
If I up the migration-threshold then service restarts and IP does not move
until migration-threshold is reached.
I am guessing this could maybe be achieved with some location rule ?


>
> Thanks,
>
> Dejan
>
> >
> >
> >
> > Regards,
> >
> >
> > Marko
> >
> > *
> > *
>
> > _______________________________________________
> > 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/20101125/f41f060e/attachment-0002.htm>