A few of us have been discussing how awesome it would be to use MediaWiki-Vagrant[1] to create a portable production-like environment. This would give Mediawiki engineers a common ground from which to develop core code and/or extensions, and by coming close to mimicking Wikimedia's production environment, would hopefully reduce the amount of friction around getting features out to production. Also, this is something that we would be able to pre-package this for new engineers - imagine handing a new MediaWiki engineer a USB stick with an up-to-date MediaWiki-Vagrant instance that closely mimics production at say, a future hackathon.
We started chatting about what it would take to get us there, and identified some initial steps that we'd like to tackle at the Zürich Hackathon - namely, turning a few puppetized production services into roles that we could use in MediaWiki-Vagrant.
We've created a corresponding 'topic' on the Hackathon's topic page[2] to describe what we'd like to achieve at the Hackathon. Please review, comment, and certainly add yourself as an 'interested person' if this catches your fancy and you plan to attend the hackathon.
aren't you lost this links? :-)
1 https://www.mediawiki.org/wiki/MediaWiki-Vagrant 2 https://www.mediawiki.org/wiki/Z%C3%BCrich_Hackathon_2014
11.02.2014 06:13, Arthur Richards пишет:
A few of us have been discussing how awesome it would be to use MediaWiki-Vagrant[1] to create a portable production-like environment. This would give Mediawiki engineers a common ground from which to develop core code and/or extensions, and by coming close to mimicking Wikimedia's production environment, would hopefully reduce the amount of friction around getting features out to production. Also, this is something that we would be able to pre-package this for new engineers - imagine handing a new MediaWiki engineer a USB stick with an up-to-date MediaWiki-Vagrant instance that closely mimics production at say, a future hackathon.
We started chatting about what it would take to get us there, and identified some initial steps that we'd like to tackle at the Zürich Hackathon - namely, turning a few puppetized production services into roles that we could use in MediaWiki-Vagrant.
We've created a corresponding 'topic' on the Hackathon's topic page[2] to describe what we'd like to achieve at the Hackathon. Please review, comment, and certainly add yourself as an 'interested person' if this catches your fancy and you plan to attend the hackathon.
Argh! Thanks Pavel :)
On Mon, Feb 10, 2014 at 7:46 PM, Pavel Astakhov pastakhov@yandex.ru wrote:
aren't you lost this links? :-)
1 https://www.mediawiki.org/wiki/MediaWiki-Vagrant 2 https://www.mediawiki.org/wiki/Z%C3%BCrich_Hackathon_2014
11.02.2014 06:13, Arthur Richards пишет:
A few of us have been discussing how awesome it would be to use
MediaWiki-Vagrant[1] to create a portable production-like environment. This would give Mediawiki engineers a common ground from which to develop core code and/or extensions, and by coming close to mimicking Wikimedia's production environment, would hopefully reduce the amount of friction around getting features out to production. Also, this is something that we would be able to pre-package this for new engineers - imagine handing a new MediaWiki engineer a USB stick with an up-to-date MediaWiki-Vagrant instance that closely mimics production at say, a future hackathon.
We started chatting about what it would take to get us there, and identified some initial steps that we'd like to tackle at the Zürich Hackathon - namely, turning a few puppetized production services into roles that we could use in MediaWiki-Vagrant.
We've created a corresponding 'topic' on the Hackathon's topic page[2] to describe what we'd like to achieve at the Hackathon. Please review, comment, and certainly add yourself as an 'interested person' if this catches your fancy and you plan to attend the hackathon.
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
A few of us have been discussing how awesome it would be to use
MediaWiki-Vagrant[1] to create a portable production-like environment. This would give Mediawiki engineers a common ground from which to develop
core
code and/or extensions, and by coming close to mimicking Wikimedia's production environment, would hopefully reduce the amount of friction around getting features out to production. Also, this is something that
we
would be able to pre-package this for new engineers - imagine handing a new MediaWiki engineer a USB stick with an up-to-date MediaWiki-Vagrant instance that closely mimics production at say, a future hackathon.
We started chatting about what it would take to get us there, and identified some initial steps that we'd like to tackle at the Zürich Hackathon - namely, turning a few puppetized production services into roles that we could use in MediaWiki-Vagrant.
We've created a corresponding 'topic' on the Hackathon's topic page[2]
to
describe what we'd like to achieve at the Hackathon. Please review, comment, and certainly add yourself as an 'interested person' if this catches your fancy and you plan to attend the hackathon.
I am keeping my options open for the hackathon but wanted to support this effort enthusiastically. And to mention that the analytics team loves mediawiki-vagrant and tries to get most of its projects integrated with it as roles.
One thing I'd be interested in is to hear how Linux folks are installing vagrant / virtualbox. I've not been able to "vagrant up" my mediawiki-vagrant since I upgraded to Ubuntu 13.10 and I've heard of at least two other people with the same experience. Maybe 14.04 will just solve all that, but it's worth looking into so we can post any gotchas in the install instructions.
On Tue, Feb 11, 2014 at 2:33 PM, Dan Andreescu dandreescu@wikimedia.orgwrote:
One thing I'd be interested in is to hear how Linux folks are installing vagrant / virtualbox. I've not been able to "vagrant up" my mediawiki-vagrant since I upgraded to Ubuntu 13.10 and I've heard of at least two other people with the same experience. Maybe 14.04 will just solve all that, but it's worth looking into so we can post any gotchas in the install instructions.
I can't comment about Ubuntu, but using Debian Sid I was finally able to get it to work this morning.
All I had to do was apt-get install virtualbox-dkms and vagrant. Versions here are 4.3.2-dfsg-1 for virtualbox, 1.4.3-1 for vagrant, and 3.12.9-1 for the kernel.
On Tue, Feb 11, 2014 at 2:51 PM, Brad Jorsch (Anomie) <bjorsch@wikimedia.org
wrote:
On Tue, Feb 11, 2014 at 2:33 PM, Dan Andreescu <dandreescu@wikimedia.org
wrote:
One thing I'd be interested in is to hear how Linux folks are installing vagrant / virtualbox. I've not been able to "vagrant up" my mediawiki-vagrant since I upgraded to Ubuntu 13.10 and I've heard of at least two other people with the same experience. Maybe 14.04 will just solve all that, but it's worth looking into so we can post any gotchas in the install instructions.
I can't comment about Ubuntu, but using Debian Sid I was finally able to get it to work this morning.
All I had to do was apt-get install virtualbox-dkms and vagrant. Versions here are 4.3.2-dfsg-1 for virtualbox, 1.4.3-1 for vagrant, and 3.12.9-1 for the kernel.
Thanks Brad. Those versions didn't work for me so I finally stopped being lazy and looked into it. It was user error (well, sort of). VT-x was disabled in my BIOS. Added a note in the README: https://gerrit.wikimedia.org/r/#/c/112800/
On 02/10/2014 04:13 PM, Arthur Richards wrote:
A few of us have been discussing how awesome it would be to use MediaWiki-Vagrant[1] to create a portable production-like environment.
We recently started a push on this by packaging Parsoid and other services (rt test server, mathoid, ..) as Debian packages. This makes the installation in a Debian/Ubuntu environment as easy as 'apt-get install parsoid'.
An important advantage is that these packages are also directly usable for hosted virtual machines commonly used by third party wiki installs. It also avoids duplicating standard packaging tasks like startup scripts, user setup, logging etc between packages and puppet, and lets puppet concentrate on managing just the differences in configurations.
Gabriel
wikitech-l@lists.wikimedia.org