Page MenuHomePhabricator

Distribution strategy option: Use Vagrant puppet modules
Closed, DeclinedPublic

Description

  • install puppet
  • apply the vagrant puppet rules using a process very similar to labsvagrant
  • does not actually use vagrant, but reuses vagrant puppet repo

Security upgrades

  • ?

Major version upgrades

  • vagrant up? Will this run update scripts etc?

Details: see @bd808's post below.

Event Timeline

GWicke raised the priority of this task from to Needs Triage.
GWicke updated the task description. (Show Details)
GWicke added subscribers: Spage, Worden.lee, scfc and 12 others.

No puppet master is actually needed. The way that this works for labs-vagrant is that the labs puppet rules clone mediawiki/vagrant.git to /srv/vagrant (which is symlinked to /vagrant for path compatibility with a Vagrant managed VM) and then [[https://github.com/wikimedia/mediawiki-vagrant/blob/1e069e45ba10c3d5a6ee1db0667f8a14a4699b0e/lib/labs-vagrant.rb#L65-L77|labs-vagrant provision]] can be run to apply the Puppet rules from /srv/vagrant/puppet to the host.

One issue with reusing the MediaWiki-Vagrant puppet roles in a production environment is that the current roles configure HHVM/PHP and the wiki(s) for easier development. This means verbose logging and other tuning settings that are more friendly to rapid iteration of code changes than to robust request service.

There is a project called librarian-puppet that might be interesting to explore for sharing of Puppet code tailored for running a MediaWiki stack between multiple environments and consumers. GitHub's Boxen project for managing OS X laptops with Puppet uses this framework to make mixing and matching Puppet config easier.

Arlolra triaged this task as Medium priority.Apr 2 2015, 5:05 PM
Arlolra added a subscriber: Arlolra.