Changes

As a contributor to [https://github.com/enterprisemediawiki/meza Meza], and developer of [[QualityBox]], we've been closely following the efforts in the [[MediaWiki]] community around easier/automated deployments of MediaWiki. Actually, it's a goal of the [https://mwstake.org MWStakeholders Group]. And, it's a crucial aspect of the whole [https://www.mediawiki.org/wiki/Wikimedia_Technology/Goals/2017-18_Q3 2017 Wikimedia Technology Department Goals] since at least 2018. Here is a list of some of the efforts and projects within and outside the WMF for automating deployments of MediaWiki:

It should be noted that the WMF uses Puppet for configuration management(See the [https://phabricator.wikimedia.org/diffusion/OMWC/ operations/mediawiki-config repo]), and <strike>[https://wikitech.wikimedia.org/wiki/Scap3 Scap3] (which is used in [https://wikitech.wikimedia.org/wiki/SWAT_deploys SWAT])</strike> (obsolete) 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].