|Thread title||Replies||Last modified|
|Create account||2||15:47, 15 April 2013|
|Feature justification, goals, & process||0||20:44, 3 January 2013|
|What is the conditions to have an instance for an extension ?||3||18:47, 24 July 2012|
|Some things still to be automated?||1||04:56, 27 February 2012|
|Request: rough schedule||0||16:03, 8 February 2012|
|Schedule for bots on Tool Labs||5||14:55, 16 December 2011|
|Root access to the production cluster?||2||02:25, 6 December 2011|
The page says,
'You can create a Labs account to do MediaWiki development, tools, or analytics by simply filling out the account creation form.'
But when I submit that account creation form, I get the error message mentioned in this note from the page bottom:
- The error message "There was either an authentication database error or you are not allowed to update your external account." generally indicates an invalid shell account name was used (see bug 16524).'
For shell account name I tried 'roger', 'rogehc' and 'rogervoy' but none worked; all produced the error indicated in the above note. How can I create an account? I do not have shell access nor obviously any shell account name. Is that a prerequisite?
Hi, For the moment, I'm testing my extension with phpunit and tomorrow with selenium I have to install a special software on the server. So I created a container for that in openvz. Now, the extension is also in Gerrit. My extension has it the conditions to create an new instance (only during test) in Wikimedia Labs ? Can I use a container built with OpenVz in Wikimedia Labs ? Thanks
We only support KVM virtual machines at the moment. You can start working in Labs during development phases as well. You don't need to wait until you've finished it. You'll need to request an account and a project.
The project is in Gerrit : mediawiki/extensions/LinkedWiki and I have my account in gerrit and Wikimedia Lab. What next ? Thanks
I have an instance set up, but as I recall it was not possible to create an "instance" without being part of a "project", and adding me to a project required manual intervention.
This is the intention. By default you have no access. You must request a project, or ask to be added to a project by a current member. Also, you must be in the sysadmin role to create/delete instances. Someone already in the sysadmin role of a project can add you to the role.
The concept is for Labs to be a community, and for the community to maintain most actions.
Could Ryan, CT, or Andrew please add a rough Labs timeline either to the roadmap on this page or to the general engineering roadmap page? That'll make it easier for me to help volunteers understand when they'll, for example, be able to get a turnkey MediaWiki development environment. Thanks!
Is there a timeline for when bots may be able to run on the cluster? I ask because one of our most active anti-vandalism bots is down because the volunteer was unable to afford hosting. And there's been a request to see if the bot could be run on the Tool Labs. Thanks.
Hi, we are now in process of setting up this part of labs, does the operator have access to wikimedia svn? It's possible to run a bot there but with a lot of limitations
I'd also like to know how feasible it would be for me to move CorenSearchBot there. It's currently running on my own infrastructure, and I have no problem with doing so indefinitely, but since that bot is being relied on by the project for some critical copyright work, it'd probably be best if it lived somewhere someone could take over if I could no longer manage it.
That said, it's not lightweight; at peak hours it can eat up a whole IA64 core's worth of processing power. Coren 15:59, 6 December 2011 (UTC)
@Petrb, I just wanted to thank you very kindly for all your work here and especially for your help with the bots. I've made an extra donation to the WMF in your honor. Thanks very much.
It states We'd like to have an environment where anyone can eventually become root, even on our production cluster. Ummmm. I guessing/hoping there are all sorts of safeguards in place and that root access to the prodcution cluster would be only for highly trusted users that have a specific need for root. I was just hoping for a bit of clarification on that. Other than that, I think this sounds like a great idea and think it could be a huge benefit to the community. Thanks.
Well, just from having a labs account, it's possible to make root level changes in the production cluster. We have our puppet configuration in a public repository, and having an account allows contributors to push changes to the repository. When the changes are code reviewed, they can be deployed to production.
Otherwise, though, we already have volunteers with root access on our production cluster. Our beginnings were founded in volunteers being root, and I'd like to continue that tradition. Over time, by contributing to the labs environment, contributors should be able to gain privileges. I believe that it should be possible for well trusted contributors to be given higher privileges, including privileges in the production cluster.
There are a number of safeguards in the labs environment to safely give out higher levels of permissions over time.
Thanks for the reply, Ryan. I also must thank you, and everybody else at the WMF, for all the support you've given us. I think this will be really helpful for our bot operators and the volunteers that write all those useful tools.
I knew we had a few volunteers with root, I just didn't realize that things were that open. I guess it makes sense since we're a volunteer run organization. Anyhoo, thanks for the clarification. Best regards. - Hydroxonium (T•C• ) 02:25, 6 December 2011 (UTC)