Projects developed in Puppet
Oct 4 2018
we no longer use a puppet module for phabricator
Jun 15 2018
Oct 3 2017
Now deployed on all machines.
Sep 12 2017
That's implemented now; it's been deployed on the workers, and should kick in during the next run of the apt periodic runner (i.e. during the night).
Sep 11 2017
(IIRC upgrades that requires interaction, e.g., conffile changes, are blacklisted by default by unattended-upgrades, but this requires double-checking.)
May 5 2017
The icinga configuration is now in puppet.
Feb 12 2017
Oct 6 2016
The puppet config for workers is now done in the swh profile.
Aug 19 2016
Closed by rSPPROF364c82ba829c
Aug 7 2016
Aug 2 2016
I'm a bit nervous about importing a puppet module with a long-lived (> 1 year) develop branch that is 160 commits ahead of master, but it seems to be the reasonable thing to do in the long run...
Jul 27 2016
Jul 8 2016
Jul 7 2016
Jun 8 2016
May 31 2016
May 20 2016
Ready to be deployed on banco.
May 13 2016
Note that there are at least 2 separate sub-tasks here, with potentially different priorities:
May 12 2016
May 5 2016
Apr 28 2016
Not there yet, but rSENV5c4dfd036344 added a bin/deploy-on helper script in the puppet-environment repo that goes through the hoops of 1) deploying the recipes on puppet master, 2) doing a test run on the given node, 3) ask for confirmation, 4) do a real deployment on the node if user confirmed.
Apr 27 2016
(21:34:47) olasd: right now when you push a repo in the puppet environment you need to run deploy.sh by hand
(21:34:56) olasd: which is boring
(21:35:44) olasd: but I don't think we can do much better
(21:36:35) olasd: except having an http service we can trigger from phabricator and running as root on the other end
(21:36:37) olasd: which doesn't look very appealing
(21:37:50) olasd: we should probably be able to make the puppet manifests modifiable to the puppet user only but that's still root equivalent in the end
(21:38:30) olasd: you can paste that to the ticket if you'd like; I'm away from forge credentials