Last modified: 2014-09-01 02:34:33 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T53556, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 51556 - Investigate Linux containers
Investigate Linux containers
Status: RESOLVED FIXED
Product: MediaWiki-Vagrant
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Normal enhancement
: ---
Assigned To: Bryan Davis
:
Depends on:
Blocks: 45499 51492 48407
  Show dependency treegraph
 
Reported: 2013-07-17 17:33 UTC by Ori Livneh
Modified: 2014-09-01 02:34 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Ori Livneh 2013-07-17 17:33:34 UTC
Docker (http://www.docker.io/) is purported to work well with Puppet and Vagrant. The Docker folk recommend Vagrant for running Docker on non-Linux hosts, and they're apparently working on a docker Vagrant provider. (A Vagrant 'provider' is a piece of middleware that tells Vagrant how to talk with a virtualization platform, be it VirtualBox or AWS).

It'd be nice if the Puppet codebase for MediaWiki-Vagrant provisioned a container. For people who use VirtualBox, the additional isolation won't be beneficial, but it won't cost them much either, since containers are reputed to be very efficient, by dint of some low-level support for containers in the Linux kernel. Containers provide quite a lot of benefit for use-cases that need isolation but not virtualization, which is any environment that is already running Linux, like Jenkins or Labs.

Containers are also increasingly popular for PaaS deployments, so there's at least the possibility that the work will pay off in modernizing the process of deploying MediaWiki to cloud platforms.
Comment 1 Matthew Flaschen 2013-07-23 09:52:03 UTC
If there's no clear benefit to it, we should think about whether it makes sense to do by default.  The goal of MediaWiki-Vagrant is to make a dev environment that (where possible) roughly resembles production.  It should go without saying that we generally want this to perform as well as possible for the developer.
Comment 2 Andre Klapper 2013-09-11 22:45:31 UTC
[mass-moving from Tools>MediaWiki-Vagrant to separate product. See bug 54041. Filter bugmail on this comment.]
Comment 3 Gerrit Notification Bot 2014-08-31 23:49:19 UTC
Change 157633 had a related patch set uploaded by BryanDavis:
Add support for Docker

https://gerrit.wikimedia.org/r/157633
Comment 4 Gerrit Notification Bot 2014-09-01 01:35:29 UTC
Change 157633 merged by jenkins-bot:
Add support for Docker

https://gerrit.wikimedia.org/r/157633
Comment 5 Bryan Davis 2014-09-01 02:34:33 UTC
We now have code to support the Docker provider in Vagrant.

We will not be making lxc/Docker required at this point. The folks that manage the Docker project seem to be much more interested in the single executable per container model. It should be possible to provision an entire MediaWiki stack (apache, database, cache, jobrunner) using multiple Docker containers in the way that Docker would like, but it would be a separate project from MediaWiki-Vagrant.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links