netdev - Re: [PATCH RFC 00/24] IPVS: Add first IPv6 support to IPVS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 23 Aug 2008 19:13:09 -0700 (PDT)
From:	Joseph Mack NA3T <jmack@...d.net>
To:	Graeme Fowler <graeme@...emef.net>
cc:	Julius Volz <juliusv@...gle.com>,
	Sven Wegener <sven.wegener@...aler.net>,
	Simon Horman <horms@...ge.net.au>, netdev@...r.kernel.org,
	lvs-devel@...r.kernel.org, kaber@...sh.net, vbusam@...gle.com
Subject: Re: [PATCH RFC 00/24] IPVS: Add first IPv6 support to IPVS

On Sat, 23 Aug 2008, Graeme Fowler wrote:

>> I don't think we should promise anything.
>
> Well, it was just a suggestion. It'd be nice, I reckon, to 
> be able to say to people on lvs-users who ask us that 
> "yes, this is currently being worked on" at the very 
> least.

If you say that then people will expect that it will 
eventually be released and will work, and be documented and 
we'll be able to help people get it working when it arrives.

A lot of stuff has been "worked on", but not tested or 
released. Horms has piles of stuff. Jason Stubbs has working 
code for lvs hooked into PREROUTING, a great step forward in 
my estimate, but has disappeared off the mailing list. If 
you tell people all this code is out there somewhere, being 
worked on, are you then prepared to tell them that you don't 
have the code, or that no-one's tested it, and there's no 
documentation and you haven't a clue how to set it up, and 
then try to help them install it and get it going? I'm quite 
prepared to believe that you can get Horms version of lvs 
hooked into FORWARD working and help people with it, but I 
can't. There's been more code written for LVS that's never 
seen the light of day, than has ever been released. I 
wouldn't want the LVS mailing list to become famous as a 
list of promises that are not kept.

Even code that's been tested by the author and released 
doesn't get used. The -SH scheduler sat untouched for years, 
because no-one knew how to use it. Someone spelunking the 
code, figured out how to configure it.

I still have no clue what LBLC does and it's been out for 
years.

> It might stop people bleating, as they currently do 
> (albeit rarely).

No-one, who is running LVS as part of his business, and who 
monitors the mailing list daily for at least a year, never 
helping anyone, waiting for a mention of the -SH scheduler, 
so that he remind everyone that the clueless LVS developers 
have not fixed his -SH problem (and that he has no intention 
of fixing it himself, or getting anyone under his command to 
fix it either) and if we don't do something pronto, he'll go 
to a commercial loadbalancer, is entitled to bleat.

Joe
-- 
Joseph Mack NA3T EME(B,D), FM05lw North Carolina
jmack (at) wm7d (dot) net - azimuthal equidistant map
generator at http://www.wm7d.net/azproj.shtml
Homepage http://www.austintek.com/ It's GNU/Linux!
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html