I think its the wrong way to how the migration is done. Currently the plan is to disabled toolserver at the same time as tool Labs is full available.
I am running very complex tools and queries which are highly optimized for the toolserver infrastructure so that results are returned in an acceptable time. Migrating these tools to a new environment would take very much time. So to run these tools without an outage there need to be along time both projects must be available.
Why is WMF not helping maintaining parts of the toolserver? My impression is that most of load problems caused on the toolserver are database server problems. Many queries are very complex for the mysql database to handle because they are not key based (and they cannot be rewritten to be key based). Why can WMF not maintain only these database replication servers in short-term and make them accessable for toolserver user? Even if these are only rr-server on the first step this would be a big benefit. Yesterday is learned that wmf exmploys 90+ people that should have much experience for administration servers. After sql servers are maintained by wmf admins and hardware the current toolserver database server could be reused for other parts (maybe as webserver).
Btw: On sunday i submitted a critical bug to bugzilla because since saturday my interwiki bot shows that there must be some misconfigured api squids (perhaps because they are out of sync). Nobody of these 90 wmf admins has taken care of this bug until now. Maybe solving this is not explicitly contained in the job descrition of most of these admins and so they do not get a point for their year goals. Toolserver also had a problem on sunday and volunteer admin DaB. solved this problem within the red-letter day.
Merlissimo
Am 25.09.2012 15:20, schrieb Thehelpfulone:
On 25 September 2012 14:15, Ariel T. Glenn <ariel@wikimedia.org mailto:ariel@wikimedia.org> wrote:
It might be helpful to put together a list of functions that the toolserver supports but that labs currently does not; such a list could serve as a basis for talks with the WMF. Perhaps the labs folks could makes some guesses at when those functions would be available and stable there, which would give everyone a better idea about how long the transition would realistically take. If I am not mistaken, one of the big items is the ability to run expensive db queries without impacting production. I don't believe this is possible from labs right now, and I'm not sure what their plans are for that. Ariel p.s. this post is by me as a former toolserver user, having nothing to do with my status as a wmf staff member etc.There is a partial list at http://www.mediawiki.org/wiki/Wikimedia_Labs/Toolserver_features_wanted. According to the milestones at http://www.mediawiki.org/wiki/Wikimedia_Engineering/2012-13_Goals#Milestones..., we should be expecting database replication from production and user databases in January-March 2013.
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette