Cetateanu Im going to be nice in how I say this, DO NOT DEMAND things from
developers. If dev says they are not ready THEY ARE NOT READY. please also
consider that these developers run one of the top ten websites on the
internet, so they must be doing it right for the most part or the servers
would be a smoking pile of rubble. There are a lot more complex and unseen
factors that exist on large scale server arrays such as wikimedia's than
what your recommending. If either of your ideas where feasible with the
current system it would have been taken care of. Here is a suggestion, LET
THE DEVELOPERS DEVELOP a good way to implement your request without breaking
things
On Fri, Jul 10, 2009 at 3:47 PM, Cetateanu Moldovanu
<cetateanumd(a)gmail.com>wrote;wrote:
Hello Mister Vibber,
I'm glad to see you already made a plan, I supose you know the best
mediawiki and wikipedia architecture, aren't there anybody else to execute
those points from that plan ?
Even if those points sounds havy, since the number of articles&files from
mo
is not so high, I'm sure you can do all those points in a day or two of
work.
for each of 22 clusters
I'm sure you
have a script to execute a command on all clusters at once and
see the results.
Or in the meantime you build a "infrastructure for conveniently renaming
sites", you can put in place a temporary solution that is easier to build.
You could just make a new vhost(mo-cyrill) that point to the same dir as
mo.
And for mo you could make a htaccess (or equivalent) that would redirect
all
the request to the mo-cyrill (with a script that get REQUEST_URI and output
a redirect header).
Hope to hear you soon.
Best regards,
On Thu, Jul 9, 2009 at 2:03 AM, Brion Vibber <brion(a)wikimedia.org> wrote:
Hi Cetateanu --
As replied previously, we don't yet have infrastructure for conveniently
renaming sites. Given that the site has been locked for years and there's
nothing to replace it with at
mo.wikipedia.org, it's no higher on our
priority list than the other sites that have language code renames
pending.
Since we've been in the midst of a slow migration of external text
storage
as well, it's slid farther back on the burner
than planned. I'll see if
we
can make sure it's on the radar at least...
The problem isn't intractable, but merely inconvenient, and due to the
number of sites & databases needing renaming it needs to be scripted and
tested for safety first:
* Ensure language/localization files have been updated for new language
code
* Lock site
* Rename public file storage subdirectories
* Rename private file storage subdirectories
* Ensure all site config entries have been updated for new language code
* Rename core database on primary database cluster (create new database,
rename all tables, drop old empty database)
* Ensure that all slave databases were properly updated
* Rename blob databases on all external storage clusters (for each of 22
clusters, create new database, rename all tables, drop old empty
databases)
* Ensure that all slave databases were properly updated
* Make sure it didn't break anything _else_...
* Unlock site
* Rename or move data dump archives
* Check if anything else needs cleaning up in recent changes channels,
interwiki links, or other output.
-- brion vibber (brion @
wikimedia.org)
Cetateanu Moldovanu wrote:
> *Hi, I want to remind you that on 26 Nov 2008 **
>
promised that subdomain name mo will become mo-cyrl, it's July now
> and mo is still not yet renamed.*
>
> * *
> *
> If you cannot rename please delete it altogether.
> Hope to get a ETA, or to know at which point is the progress.
> Brion Vibber and his superiors, please make a room for this task to be
> done, also I (as a programmer) can volunteer to help you do this thing
if
you have
a lack of resources !
IT'S IMPORTANT !
*
_______________________________________________
foundation-l mailing list
foundation-l(a)lists.wikimedia.org
Unsubscribe:
https://lists.wikimedia.org/mailman/listinfo/foundation-l