Re: [Toolserver-l] Wikidata tables
> FWIW, I have implemented a query-able stand-alone web server that keeps all > of the wikidata property-item-links in memory. This uses the wikidata dumps That does not sound too terribly scalable. I did the same thing (custom webserver, data kept in memory) for the map labels of my WikiMiniAtlas, and had to abandon this in order to be able to support more languages. And my data is only a subset of what I expect to show up in WikiData. On top of that not being able to join data from there with other DBs is a serious deficiency. Same goes for the suggestion to "just use the API". Daniel ___ 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
[Toolserver-l] Department of the reporting of statuses
What's the worst that could happen? The big news this week is the replacement of Gluster as the provider of shared storage by NFS for the tools project. In doing so, we're going to gain a great deal of extra stability, and quite a bit of performance. In addition, there is now an automatic timetravel snapshot feature allowing users to look at the filesystem as it was during snapshots spanning: once an hour for the past three hours, once a day for the past three days, and two weekly snapshots (on Sundays). That said, NFS is robust but does not scale as much as we would like in the longer term; we will keep investigating clustered storage solutions for the future, with an eye to returning to it once we find a solution that is (a) no less robust than NFS, (b) no less reliable than the current storage and (c) at least as good from a performance standpoint. Technically, this storage is already available to all projects but the configuration necessary to /replace/ gluster with it would generally require a per-project outage. (Involving copying the contents of the previous store to the new one, and substituting one mount point for another -- a process which running processes can generally not cope with). In practice, the tools project will be the first transition "victim", with an outage tomorrow to make the switchover. Sadly, the process is necessarily disruptive and currently running processes will be affected (see below for details). As secondary news, thanks to the unwavering efforts of Asher, the database replication is now at a point where we are actually selecting what, exactly, is going to be replicated. Things are progressing there at a fair clip and we're still sticking pretty close to schedule. More news on that topic next week. === Planned outage === When: Tuesday April 23 at 18:00 UTC Duration: 1 hour Impact: * Jobs running on the grid engine will be stopped, and execution nodes will be temporarily disabled; * The login server will be restarted during the window, ending active sessions; * The web service will be unavailable during the maintenance window; and * Running processes not scheduled through the grid engine will be killed. Recovery plan: In case of unplanned failure during the maintenance window, configuration will be rolled back to the current version (that is, the gluster-based project storage will remain in place) and a new window will be planned after postmortem. -- Marc ___ 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
[Toolserver-l] Tool Labs: Summary of Feedback on the Draft for the Roadmap
Hi all! Let me shortly summarize the comments on the roadmap's discussion pages: There were no comments about the actual roadmap but feedback concerning these two topics: 1) What's going to migrate and what isn't? * Until now, it's not clear which tools will not be able to move. Or which maintainers might decide not to move and why. People are curious about this but tool maintainers would have to talk about it for us to find out. 2) Bad Tool Labs experience: * How fast is the account creation process right now? A tool maintainer reported that he spontaneously had some time to think about migrating. He requested an account but then waited for two weeks to get it. For people working on tools in their spare time this is too long. * Documentation has to be improved! Good overviews are needed as well as a detailed documentation of everything relevant to working in Tool Labs. * An example: You get strange messages and can't find any information on them, e.g. this one: "Your user rights were changed by Andrew Bogott. You are now a member of this group: shell. Learn more". By clicking onto it, you get a list of permissions: "loginviashell". There is a red link pointing to "Wikitech:Shell". The user is confused. * Who is responsible for documentation? (I'm not sure I answered this correctly: It's not clear to me how much the Tool Labs docs overlap with general Labs docs and who is responsible for that part. Or is the Tool Labs documentation isolated from the rest???) Cheers, Silke 2013/4/19 Silke Meyer : > Hi all! > > As you know Wikimedia Deutschland has the mandate to create a roadmap > for the availability of features on Wikimedia Labs / Tool Labs that are > currently available on the Toolserver until the next membership assembly > (May 25th). I have worked on this for the last weeks and now published a > draft. I would like to get your feedback on this draft to make sure it > is sound and nothing vital is missing. The current version is not final > but hopefully very close to what will be presented at the membership > assembly next month. > > The plan has been drafted in close cooperation with the responsible > people at the Wikimedia Foundation. It still needs a final ok from them > though. > > You can find the drafts at: > > English version: http://www.mediawiki.org/wiki/Tool_Labs/Roadmap_en > > German version: http://www.mediawiki.org/wiki/Tool_Labs/Roadmap_de > > To not spread out discussions too far please use the discussion pages of > the above two pages for comments, suggestions and corrections. > > Cheers, Silke > > -- > Silke Meyer > Internes IT-Management und Projektmanagement Toolserver > > Wikimedia Deutschland e.V. | Obentrautstr. 72 | 10963 Berlin > Tel. (030) 219 158 260 > > http://wikimedia.de > > Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V. > Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg > unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt > für Körperschaften I Berlin, Steuernummer 27/681/51985. -- Silke Meyer Internes IT-Management und Projektmanagement Toolserver Wikimedia Deutschland e.V. | Obentrautstr. 72 | 10963 Berlin Tel. (030) 219 158 260 http://wikimedia.de Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985. ___ 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
