Welcome to the New Slashdot Chicago Cluster 149
Thanks to everyone who tested on Friday, as well as to all of SourceForge's netops crew, our corporate overlords at SourceForge for paying the bill, and of course all the engineers on Slashteam- Jamie McCarthy, Tim Vroom, Chris Nandor, Chris Brown, and Scott Collins, we are now running on the new iron in a cage in Chicago. We'll run a story in a few days about the ridiculously overpowered new hardware we have now, but now is the part of sprockets where we dance.
Down time? (Score:2, Interesting)
Obvious question... (Score:5, Interesting)
Or auction them off to your readership for charity?
description of the process? (Score:5, Interesting)
Do you guys have a description of the migration steps hidden away in a journal somewhere?
Appreciatively,
Seth
Re:!news (Score:3, Interesting)
Actually, this is news. Slashdot is snappy as hell for me, which I haven't seen in a long time. Nice work.
Oh wait, that just means I'm going to run into the lameness filter that much faster...
Paying the bills (Score:4, Interesting)
Unimaginative, tawdry, pale and ineffectual praise (Score:3, Interesting)
IPv6 please (Score:5, Interesting)
Could you please add an IPv6 VIP to slashdot now that you've got this move out of the way? I mean, it's 2008 already
Have you ran any stats on your dns logs to see what percentage are requests for quad-As?
If you're nervous about suddenly blackholing because of misconfigured remote sites, perhaps you could add an ipv6beta.slashdot.org site à la ipv6.google.com? Or, I read of a long-running test a website had been running where a third of clients were served a one-pixel image from a hostname with a single AAAA record, another third a dual record, and finally a single A record to test against reachability problems.
So, I'm sure you're all smart and working on it and I'll just have to keep patiently waiting, but I'll be so pleased when your v6 integration matches undeadly.org.