Puppet recipes used to administer Software Heritage infrastructure, i.e., stuff in all puppet-* repositories
Oct 4 2018
we no longer use a puppet module for phabricator
Sep 14 2018
That also implies some dangling files clean up.
Jun 15 2018
Dec 20 2017
Dec 19 2017
Dec 7 2017
Nov 28 2017
As for the icinga2 issue, this was fixed with:
The fqdn must have been set wrong at some point during the deployment.
There was a duplicate node definition in puppetdb for a worker03.euwest.azure.euwest.azure.internal.softwareheritage.org node. The fqdn must have been set wrong at some point during the deployment.
Nov 23 2017
Oh yeah, also for icinga, we are possibly quite late there:
Oct 3 2017
Now deployed on all machines.
Sep 15 2017
AFAICT this is now done as part of the generalization of default icinga2 checks on all our machines. (Please reopen if it's not the case.)
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.
Mar 15 2017
Mar 14 2017
Feb 12 2017
Oct 11 2016
Oct 10 2016
Oct 6 2016
The puppet config for workers is now done in the swh profile.