Re: csswg.org / fxtf.org scheduled maintenance - test repository refactoring

On May 29, 2014, at 5:22 PM, Peter Linss <peter.linss@hp.com> wrote:

> 
> On May 29, 2014, at 4:43 PM, Peter Linss <peter.linss@hp.com> wrote:
> 
>> On May 29, 2014, at 11:58 AM, Peter Linss <peter.linss@hp.com> wrote:
>> 
>>> I'm planning on taking the server running csswg.org and fxtf.org down this afternoon in order to migrate the machine to a new host[1]. I plan on starting around 4pm PDT and I expect it to take less than an hour (most of the time will be performing backups).
>>> 
>>> Note that in addition to *.csswg.org and *.fxtf.org being down during this interval, dev.w3.org/csswg and dev.w3.org/fxtf will also appear down as they proxy to drafts.csswg.org and drafts.fxtf.org respectively.
>>> 
>>> The draft mercurial repositories at dvcs.w3.org/hg/csswg and dvcs.w3.org/hg/fxtf will be unaffected, but changes will obviously not appear in dev.w3.org until the migration is complete.
>>> 
>>> After the migration is complete, I plan on landing the test repository refactoring work that Rebecca has done[2]. This will involve taking Shepherd offline for several hours for some database maintenance.
>>> 
>>> I'll send out another email just before I take the machine offline and another when the work is complete.
>>> 
>>> Peter
>>> 
>>> 
>>> [1] Our hosting provider, Linode, has recently installed a fleet of new machines with more RAM, faster processors, enterprise grade SSD-RAID storage and 40GB internet connections. Should give a nice performance boost.
>>> [2] http://lists.w3.org/Archives/Public/public-css-testsuite/2014May/0000.html
>> 
>> 
>> The first backup of the server (a live snapshot) is currently running and should finish around 5:15pm PDT. Once this is done the server will go offline for another backup and the migration.
>> 
> 
> The server is going offline now.

The migration is complete and the server is back online. As always, if you notice any issues, please let me know immediately.

Shepherd and the test repository are now going offline for maintenance and refactoring.