As a Cloud VPS user I want to use Puppet roles to make it easy to set up virtual machines. However many of the current Puppet roles assume a more complex or WMF-specific setup, e.g. the differentiated Redis roles when all I want is a standalone Redis server. Redis is one example, but in general we should see what software packages people are using for Cloud VPS and what "generic" Puppet roles we could create.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T197906 Come up with list of software packages to create generic puppet roles for | |||
| Declined | None | T197907 Create generic Redis puppet role |
Event Timeline
Comment Actions
T246017: CodeSearch Docker containers not starting or failing after start because of iptables network overlay issues made me think that a ::profile::cloudvps::docker manifest could be a good idea. There are at least 2 Cloud VPS projects (integration and codesearch) which are deploying Docker on instances and using related but slightly different work arounds to keep ferm and Docker from fighting over iptables rules which are needed for north-south communication with the Docker containers.
Comment Actions
FYI we're now at a third VPS project (libraryupgrader) copy/pasting the docker stuff.
Comment Actions
Boldly closing. The direction we're going with Puppet (see T285539 and others) seems to indicate that we don't want people using Puppet to provision applications unless they're familiar with it and the WMF setup around it, and for those cases generic software packages are hardly very useful.