Difference between revisions of "Automated deployment of MediaWiki"
(link to tech goals) |
(Some background on WMF config management and deploys) |
||
| Line 13: | Line 13: | ||
* [https://github.com/dataspects/meza-building-blocks Meza Building Blocks] A series of roles to add to or complement Meza by Lex Sulzer | * [https://github.com/dataspects/meza-building-blocks Meza Building Blocks] A series of roles to add to or complement Meza by Lex Sulzer | ||
| + | == Configuration Management and Deployment at WMF == | ||
| + | It should be noted that the WMF uses Puppet for configuration management, and [https://wikitech.wikimedia.org/wiki/Scap3 Scap3] (which is used in [https://wikitech.wikimedia.org/wiki/SWAT_deploys SWAT]) for [https://wikitech.wikimedia.org/wiki/Deployments deployments]. There is the [https://wikitech.wikimedia.org/wiki/Portal:Cloud_VPS Cloud VPS] which is powered by [[wp:OpenStack]] for projects related to the [https://meta.wikimedia.org/wiki/Wikimedia_movement Wikimedia movement]. The environment includes access to a variety of [https://wikitech.wikimedia.org/wiki/Portal:Data_Services data services]. Cloud VPS is meant to make it easier for developers and system administrators to try out improvements to Wikimedia infrastructure (including MediaWiki), power research and analytics, and host projects that are not viable in the [https://wikitech.wikimedia.org/wiki/Portal:Toolforge Toolforge] environment. Virtual machines running on Cloud VPS are subject to the [https://wikitech.wikimedia.org/wiki/Portal:Wikimedia_VPS/instance_lifecycle instance lifecycle]. | ||
| + | === Puppet === | ||
| + | |||
| + | * https://wikitech.wikimedia.org/wiki/Puppet | ||
| + | * https://wikitech.wikimedia.org/wiki/Puppet_coding | ||
| + | |||
| + | |||
| + | == Config Settings == | ||
With any automation tooling and deployment, you will inevitably need to refer to the long list of [https://www.mediawiki.org/wiki/Manual:Configuration_settings MediaWiki Configuration settings]. | With any automation tooling and deployment, you will inevitably need to refer to the long list of [https://www.mediawiki.org/wiki/Manual:Configuration_settings MediaWiki Configuration settings]. | ||
Revision as of 13:36, 23 May 2018
As a contributor to Meza, and developer of QualityBox, I'm closely following the efforts in the MediaWiki community around easier/automated deployments of MediaWiki. Actually, it's a goal of the MWStakeholders Group. And, it's a crucial aspect of the whole Wikimedia Technology Department Goals. Here is a list of some of the efforts and projects within and outside the WMF for automating deployments of MediaWiki
- Official Docker repository of MediaWiki
- Phabricator workboard for MediaWiki-Containers
- Addshore's GitHub repo for using Docker and MediaWiki (Developers) See also: MediaWiki API library Not exactly DevOps, but good to know/use/contribute. Addwiki repos are by Addshore, Jeroen DeDauw and Sam Wilson
- Wikimedia Git repo of the Docker official image for MediaWiki (forked from https://github.com/benhutchins/docker-mediawiki)
- Docker Library Docs
- Docker Library Docs for MediaWiki
- MediaWiki Node Services Run several MediaWiki nodejs services (RESTBase, Parsoid) in a single docker container. Useful for small / low-memory installs. By WMF's d00rman (Marko Obrovac - Croatia) and gwicke (Gabriel Wicke - Menlo Park)
- Wikimedia base docker images for production by lavagetto (Giuseppe Lavagetto - Italy)
- Set up BlueSpice MediaWiki Enterprise Distribution by lexsulzer (Lex Sulzer at Dataspects - Zurich, Switzerland)
- Dataspects' Easy System Cloning
- Meza Building Blocks A series of roles to add to or complement Meza by Lex Sulzer
Configuration Management and Deployment at WMF[edit | edit source]
It should be noted that the WMF uses Puppet for configuration management, and Scap3 (which is used in SWAT) for deployments. There is the Cloud VPS which is powered by wp:OpenStack for projects related to the Wikimedia movement. The environment includes access to a variety of data services. Cloud VPS is meant to make it easier for developers and system administrators to try out improvements to Wikimedia infrastructure (including MediaWiki), power research and analytics, and host projects that are not viable in the Toolforge environment. Virtual machines running on Cloud VPS are subject to the instance lifecycle.
Puppet[edit | edit source]
Config Settings[edit | edit source]
With any automation tooling and deployment, you will inevitably need to refer to the long list of MediaWiki Configuration settings.
