The Signpost

Technology report

Intermittent outages planned, first Wikidata client deployment

Contribute  —  
Share this
By Aude, Mono, and Jarry1250

Wikidata deployed to Hungarian Wikipedia

The Wikidata team in April 2012

The Wikidata client extension was successfully deployed to the Hungarian Wikipedia on 14 January, its team reports. The interwiki language links can now come from wikidata.org, though "manual" interwiki links remain functional, overriding those from the central repository. Although they are now little more than edit window clutter, members of the Hungarian Wikipedia community have been hesitant with regard to remove existing links, given that Wikidata-ignorant interwiki bots remain in operation, potentially re-inserting the "missing" links in the wikitext. Changes coming from Wikidata can also be seen in recent changes and in the watchlist, though they are hidden by default, marking an end to interwiki-link changes cluttering watchlists (announcement on huwiki (in Hungarian) and blog post (in English) on the Wikimedia Germany blog). Deployments to the Hebrew and Italian Wikipedias are planned for 30 January, and assuming all goes well – and communities remain receptive – the Wikidata client should have found its way onto English Wikipedia by the end of February and then onto other language Wikipedias in the following month. The Wikidata team welcomes feedback, either via the Contact the development team page on Wikidata, on #wikimedia-wikidata on IRC, or on the mailing list. In addition to Hungarian Wikipedia, the client is also enabled on test2wiki where interested users who do not speak Hungarian can test it.

Development of phase 2, relating to infobox-style data entries is progressing well, the Wikidata team reports, though again code review is likely to be a slow and arduous process and no deployment dates have yet been set. In related news, the 3 millionth Wikidata item was created on January 13: "List of mayors of Westdorpe", a large village in the Netherlands.

Intermittent outages expected during primary data centre switchover

Servers at the Ashburn data centre

The Wikimedia operations team is busy preparing to switch over the master database servers and other key infrastructure to use the Ashburn, Virginia data centre as the primary data centre. The Ashburn data centre is already serving about 90% of traffic, but this is mainly the result of it hosting caching servers which serve pages for logged-out users, as well as images, JavaScript and CSS. When Wikimedians edit a wiki, the regeneration of the pages is still handled by master database servers in the Tampa data centre. The switchover is part of an ongoing project to enable redundancy for key infrastructure; in addition, the change in "primary" centre from Tampa to Ashburn revolved around the quality of the facilities at both locations.

CT Woo, the Foundation's Director of Operations, announced the change on the wikitech-l mailing list:


In the event of an outage, Wikimedians can get updates on IRC in the #wikimedia-tech channel, or via Wikimedia's Twitter accounts @wikimedia or @wikimediatech (detailed server logs).

As the operations and core platform team are setting up new servers and infrastructure, they are taking it as an opportunity to also switchover to new deployment tools (git-deploy) and a new internal workflow for the regular code updates to the Wikimedia projects.

Echo project holds office hours

Notifications on MediaWiki.org

The Echo team held IRC office hours on January 8 where they discussed development progress on a Facebook-style notification system for editors. As previously reported, Echo, currently deployed on MediaWiki.org, provides notifications when someone edits your talk page, creates a link to an article you created, nominates it for deletion, adds maintenance tags, or reverts your edit. There will be a notifications "badge" at the top of the page, next to your user name, which can replace the "yellow" bar that users see now when you have a new talk page message. The team described how they have a "'user mention' notification in the works" which could work similar to Twitter mentions and notify you when someone mentions you on another page. The team welcomes feedback on the types of notifications to provide, although they initially have in mind new users, who are more likely to miss important events than established users. Echo may also provide a public notifications API that could be used by bots and scripts, the team said, though they, together with the community, would need to figure out how to balance ease of use of the tool while minimizing abuse and spamming with the notifications API.

Echo is available for testing on test2wiki. The Echo team plans on initial experimental deployment to English Wikipedia sometime next month (presumably of an opt-in nature). Interested editors can also stay informed and discuss with the Editor Engagement team about Echo and other projects on their new editor engagement mailing list.

Disclaimer: User:Aude is an employee of Wikimedia Germany, working on the Wikidata project.

In brief

Not all fixes may have gone live to WMF sites at the time of writing; some may not be scheduled to go live for several weeks.

+ Add a comment

Discuss this story

These comments are automatically transcluded from this article's talk page. To follow comments, add the page to your watchlist. If your comment has not appeared here, you can try purging the cache.
I'm sure operations folks are aiming for no outages and there might well be none. (hopefully) But there's some risk involved in this sort of switchover and maybe the transition isn't 100% perfect. --Aude (talk) 19:56, 16 January 2013 (UTC)[reply]
Repeating what Aude said for the most part. There isn't some gigantic, Frankenstein-style switch that can just be levered. There are a lot of moving parts and things that can go wrong. As the sayings go, "The map is not the terrain," and "No plan, however well-conceived, survives contact with the enemy."--Jorm (WMF) (talk) 20:57, 16 January 2013 (UTC)[reply]
Well if both clusters are running and synchronising before the switch over, then careful DNS migration should provide a seamless transition, provided synchronisation can be maintained. However most architectures have weak points, and atomicity is probably ours. Rich Farmbrough, 19:12, 19 January 2013 (UTC).[reply]
Good point, that. MikeLynch (talk) 17:53, 21 January 2013 (UTC)[reply]



       

The Signpost · written by many · served by Sinepost V0.9 · 🄯 CC-BY-SA 4.0