Ryan Lane wrote:
> If WMF becomes evil, fork the entire infrastructure into EC2,
> Rackspace cloud, HP cloud, etc. and bring the community operations
> people along for the ride. Hell, use the replicated databases in Labs
> to populate your database in the cloud.
Tim Landscheidt wrote:
> But the nice thing about Labs is that you can try out (re-
> plicable :-)) replication setups at no cost, and don't have
> to upfront investments on hardware, etc., so when time
> comes, you can just upload your setup to EC2 or whatever and
> have a working Wikipedia clone running in a manageable time-
This is not an easy task. Replicating the
databases is enormously
challenging (they're huge datasets in the cases of the big wikis) and
they're constantly changing. If you tried to rely on dumps alone, you'd
always be out of date by at least two weeks (assuming dumps are working
properly). Two weeks on the Internet is a lot of time.
I don't know if this is not an easy task, but you are proba-
bly right. So what? If a scenario of WMF turning rogue
couldn't bear losing two weeks of edits while saving almost
a decade, we should work on ways to incremental dumps.
In fact there are (experimental) adds/changes dumps, so while it might
not be a 5 minute procedure to get that data into your copy, and
deletions and suppressions wouldn't be covered, the amount of data that
would be lost would be pretty small.