-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Some of you may have noticed that the Subversion server has been particularly slow the last few days. For the year since we set it up, we've been hosting our Subversion repository on my personal server account, keeping it separate while we figured out the security issues and for availability if our main data center was down.
Lately the traffic has been getting too high to manage though, to the point of exceeding my personal site's bandwidth quota in release months. :)
So, Mark's set aside a machine in Amsterdam to move the repository to. I'll be running the migration tomorrow if all the setup seems to be going well. There should not be much disruption in service, though there might be some interruption as DNS changes or if there's a problem.
What you *may* see is that the SSH host key for svn.wikimedia.org will change, which will toss up warnings for developers using their svn+ssh accounts.
For OpenSSH, remove the offending line from your ~/.ssh/known_hosts file and let it recognize the new host key.
- -- brion vibber (brion @ wikimedia.org)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Brion Vibber wrote:
Some of you may have noticed that the Subversion server has been particularly slow the last few days. For the year since we set it up, we've been hosting our Subversion repository on my personal server account, keeping it separate while we figured out the security issues and for availability if our main data center was down.
Lately the traffic has been getting too high to manage though, to the point of exceeding my personal site's bandwidth quota in release months. :)
So, Mark's set aside a machine in Amsterdam to move the repository to. I'll be running the migration tomorrow if all the setup seems to be going well. There should not be much disruption in service, though there might be some interruption as DNS changes or if there's a problem.
The new server is live. It's hosted on mayflower.knams.wikimedia.org; for most people the new DNS information should already have gone through, but if not it should come through within an hour.
If you do hit the old server, svn+ssh:// connections are disabled and it won't have the latest few commits on http://.
(There was a temporary repo inconsistency because a commit slipped through on the old server before I got the lockout working properly. If you updated your repo during those few minutes, you _might_ have to check out your working copy again; if there's a problem you'll probably see an error from Subversion first, otherwise don't worry about it.)
You can get at the old server explicitly for now at http://svn.leuksman.com/
- -- brion vibber (brion @ wikimedia.org)
Brion Vibber wrote: <snip>
So, Mark's set aside a machine in Amsterdam to move the repository to. I'll be running the migration tomorrow if all the setup seems to be going well. There should not be much disruption in service, though there might be some interruption as DNS changes or if there's a problem.
The new server is live. It's hosted on mayflower.knams.wikimedia.org; for most people the new DNS information should already have gone through, but if not it should come through within an hour.
<snip doc>
Thanks for your good work Mark & Brion :)
wikitech-l@lists.wikimedia.org