Before we upgrade the puppetmaster on tools, let's make sure that nothing disastrous happens on tools-beta.
We should at the very least make sure that there are examples of all of our major instance types running in toolsbeta before upgrading. Ideally there would be actual working grind and k8s clusters there, but setting that up may be a lot of trouble.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | aborrero | T178717 Upgrade wmcs instances and masters to puppet 4.8 | |||
| Resolved | None | T177254 Upgrade to puppet 4 (4.8 or newer) | |||
| Resolved | Andrew | T178508 Update VPS puppetmasters to 4.8 or newer | |||
| Resolved | • Bstorm | T178510 Upgrade puppetmaster on toolsbeta and test |
cc: everyone who has been active in the toolsbeta project
Two things:
The puppet compilers can be deleted now that you got everything working on another host. Given that there isn't much of a grid left (I vaguely remember the regular exec nodes did not survive a migration) it's probably fair to just shutdown the rest of the hosts as well.
From the logs, toolsbeta-puppetmaster7 was created by @scfc, the puppet-compilers by me and the rest of the hosts more recently by @madhuvishy. I think we had a bunch of other exec nodes at some point, but those probably did not survive one migration or another.
The toolsbeta-puppetmaster-02 is certainly upgraded (is on stretch) and uses puppetdb as well.
I believe this is closeable.