From: Lars Marowsky-Bree <lmb@suse.de>
To: Harald Welte <laforge@netfilter.org>, bert hubert <ahu@ds9a.nl>,
Christoph Hellwig <hch@infradead.org>,
Linux Netdev List <netdev@oss.sgi.com>
Subject: Re: [PATCH 2.6] iptables CLUSTERIP target
Date: Thu, 21 Oct 2004 15:33:46 +0200 [thread overview]
Message-ID: <20041021133346.GL3911@marowsky-bree.de> (raw)
In-Reply-To: <20041021130327.GD3551@sunbeam.de.gnumonks.org>
On 2004-10-21T15:03:27, Harald Welte <laforge@netfilter.org> wrote:
> > I note with glee that CLUSTERIP implements (and improves) the evil ideas of
> > http://lartc.org/autoloadbalance.php3
>
> I didn't know about that page, but yes, indeed. I first was informed
> about this approach by Fabio Olive Leite, who was one of my colleagues
> at Conectiva (where I was 2001). He presented this approach at the
> Linux Kongress 2002:
> http://www.linux-kongress.org/2002/papers/lk2002-leite.html
>
> Later SuSE approached me if I was interested in implementing that idea,
> and that's how CLUSTERIP happened. If I'm not mistaken SuSE is already
> shipping this (at least in some beta version?) - I don't really know but
> maybe lmb can shed some light on this issue.
Yeah, I learned about it from Fabio, thought it would be a cool idea,
and eventually we sponsored Harald to make it happen. It's shipping in
SLES9, and we're adding full support for it in the 2.0 heartbeat cluster
resource manager.
It's meant to complement the LVS / mod_backhand based approaches.
If the proc file IO for communicating with the module goes away in
favour of a commandline based add/list/remove/etc interface, that would
just help to tidy up our code, so it's OK with me.
> > And yes, I've received hate mail over this from switch engineers :-)
> Why is that? They have to deal with multicast traffic, too... and I
> don't really see how this is any different.
Yeah, but with this they get a whole lot more ;-)
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX AG - A Novell company
next prev parent reply other threads:[~2004-10-21 13:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 22:38 [PATCH 2.6] iptables CLUSTERIP target Harald Welte
2004-10-20 23:18 ` YOSHIFUJI Hideaki / 吉藤英明
2004-10-21 4:40 ` David S. Miller
2004-10-21 7:44 ` Christoph Hellwig
2004-10-21 7:55 ` Christoph Hellwig
2004-10-21 9:12 ` Harald Welte
2004-10-21 9:40 ` Herbert Xu
2004-10-21 11:05 ` bert hubert
2004-10-21 13:03 ` Harald Welte
2004-10-21 13:33 ` Lars Marowsky-Bree [this message]
2004-10-21 14:25 ` Harald Welte
2004-10-21 15:08 ` bert hubert
2004-10-21 21:31 ` Allowing netlink_family to be any integer (was: [PATCH 2.6] iptables CLUSTERIP target) Herbert Xu
2004-10-21 22:53 ` Thomas Graf
2004-10-21 23:02 ` Allowing netlink_family to be any integer Ben Greear
2004-10-22 12:25 ` Allowing netlink_family to be any integer (was: [PATCH 2.6] iptables CLUSTERIP target) Herbert Xu
2004-10-22 12:53 ` jamal
2004-10-22 11:29 ` jamal
2004-10-22 11:39 ` Herbert Xu
2004-10-22 12:19 ` jamal
2004-10-22 12:32 ` Evgeniy Polyakov
2004-10-22 23:05 ` David S. Miller
2004-10-22 23:16 ` Herbert Xu
2004-10-26 3:27 ` David S. Miller
2004-10-21 16:36 ` [PATCH 2.6] iptables CLUSTERIP target, seq_file version Harald Welte
2004-10-21 17:44 ` jamal
2004-10-21 18:03 ` Harald Welte
2004-10-21 18:41 ` Henrik Nordstrom
2004-10-22 5:52 ` David S. Miller
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=20041021133346.GL3911@marowsky-bree.de \
--to=lmb@suse.de \
--cc=ahu@ds9a.nl \
--cc=hch@infradead.org \
--cc=laforge@netfilter.org \
--cc=netdev@oss.sgi.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).