From: Abhijit Menon-Sen <ams@toroid.org>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: failover with conntrackd
Date: Wed, 24 Oct 2007 18:16:32 +0000 [thread overview]
Message-ID: <20071024180432.GA4586@toroid.org> (raw)
In-Reply-To: <20071023060800.GA16481@toroid.org>
At 2007-10-23 11:38:00 +0530, ams@toroid.org wrote:
>
> But I'll try vrrpd anyway, thanks.
Ah, no. vrrpd is a non-starter, because it provides no notification when
a machine switches between primary and secondary mode. Unfortunately, I
can't use any of the three failover programs I've tried so far.
1. keepalived
- Provides notifications.
- Uses a single process for multiple interfaces, so no
synchronisation problems.
- Doesn't support MAC address takeover.
2. vrrpd
- Supports MAC address takeover.
- Uses one process per interface, but supports synchronisation
through signalling the other process when state the changes.
- Doesn't provide notifications (although Jerome Etienne's OLS
presentation suggests that he meant to implement this).
- Not very nice code; authentication partly implemented, but with
bugs and without sufficient testing.
3. ucarp
- Provides notifications.
- Reasonably nice code.
- Uses one process per interface, and provides no synchronisation
support at all.
- Does not support MAC address takeover.
I'm going to modify ucarp to change the MAC address with the state, and
to switch state on signal, so that two processes can be synchronised.
This is a lot more painful than I thought it would be.
-- ams
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2007-10-24 18:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 6:20 [LARTC] Re: failover with conntrackd Abhijit Menon-Sen
2007-10-24 18:16 ` Abhijit Menon-Sen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071024180432.GA4586@toroid.org \
--to=ams@toroid.org \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.