On Thu, Feb 3, 2011 at 6:29 PM, Tim Starling <tstarling(a)wikimedia.org> wrote:
On 04/02/11 11:39, George Herbert wrote:
Broken IPv6 routing will be evident to the
providers and users,
because nothing will work. I would expect few complaints to us...
(perhaps naively...)
There will be complaints. That's what World IPv6 Day is for, besides
raising awareness: it's a day when complaints can be handled in a
streamlined way.
Speaking of which, I don't see us on this list:
http://isoc.org/wp/worldipv6day/participants/
As a general question - is there any reason not
to move to Squid 3.1
and just be done with it that way?
Upgrading our Squid cluster is complex and time-consuming. It would be
a lot of trouble to go to just for IPv6 support.
I would recommend upgrading the Squid cluster because it's run on a
very significantly old version of the software, lacks several years
worth of general patches and maintenance, and because it's not THAT
big a deal. As I mentioned earlier in thread, I spent several years
running Squid (at the time, 3.0-stablevarious and 3.1 beta tests) at a
large site, and it didn't take that much time and effort despite
working actively with Amos and others on what turned out to be an
uninitialized buffer problem for over a year and having to compile,
tune, and seriously test all the versions from 3.0-STABLE3 through ...
19, it looks like. It was perhaps 20% of my total work for about 3
years, and would have been far less had it not been for the one
persistent bug (going from the prior 2.6 squids to 3.0 took about 3
months of me 1/4 time-ish). Performance was noticeably better with
3.0 vs 2.6 and 2.7.
Avoidance of obsolete version software rot is a key operations
technique. My current main commercial consulting customer has 5
years-past-end-of-support key enterprise infrastructure software that
they don't even quite know how to upgrade, it's so old now. Don't let
your versions get that old...
Yes, 2.7 is still getting necessary Squid project patches, latest to
STABLE9 in March 2010, but still. It's old 8-)
--
-george william herbert
george.herbert(a)gmail.com