With our recent [datacenter migration] activity, we now have two active datacenters (old in California, new in Chicago), with our systems divided between. In this interim period, we've set up tunnels between the datacenters to permit things like cronjobs to properly operate against databases in the other datacenter.
There is one component of our offering that we have had to take offline due to the migration, and that is our project purge system (used for project removal and project rename).
As it stands now, the disk where we would store the purged data is in Chicago, the site database and file releases are in Chicago, and the rest of the project data (CVS, SVN, project web, project DB, etc.) is in the California datacenter awaiting migration.
We have taken this purge system offline for two reasons:
1. Given that this code touches all of a project's data, and that data is no longer all in one place (since it is currently split between two locations), a pretty substantial amount of code adjustment would be required to get this service back online. And we would need to continue to augment this code on a regular basis as more services are cut over to the datacenter. Updating this code to work across two datacenters has no long-term benefit; these changes would be discarded when the migration is done. We would rather focus our time on the migration, since the migration has direct benefit to all end-users.
2. Our purge system creates backups (which we retain for a finite number of months as contingency), so we can readily reinstate projects. Given that this code touches all of a project's data, and that data is no longer all in one place (since it is currently split between two locations), we would be hauling a substantial additional amount of project data over the Internet in order to archive it. This doesn't seem like a good use of capacity.
Based on the fact that purge is offline, we're going to set aside requests for project removal in the mean time. We will be working for the next few weeks on the migration of project services to Chicago (starting with project web and SVN buildout). Once those migrations are complete, we'll work to bring the purge mechanism back online and clear out the backlog.
Director of Operations, SourceForge.net