T251768: Make partman/custom/no-srv-format.cfg work covered all normal DB hosts, as they all use the same partitioning scheme. The remaining db hosts and all backup hosts also need reuse recipes to be crafted.
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| install_server: Reuse partitions for dbprov* hosts | operations/puppet | production | +6 -1 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • Kormat | T251768 Make partman/custom/no-srv-format.cfg work | |||
| Resolved | • Kormat | T255768 Create reuse recipes for tendril/zarcillo/dbprov/backup hosts |
Event Timeline
Comment Actions
Note backup hosts are very unique ones- with different hardware (some have 1 or 2 external arrays of disks). I believe they were setup manually each one, as each one has different hardware and there is no standardization. That means there is really no recipe for 1st install (wipe). Aiming for "something that will not destroy data" would be enough, rather than a perfect recipe.
Comment Actions
Change 608012 had a related patch set uploaded (by Kormat; owner: Kormat):
[operations/puppet@production] install_server: Reuse partitions for dbprov* hosts
Comment Actions
tendril/zarcillo are probably unsupportable by reuse-parts. They have multiple mdraid arrays, and the documentation says that the naming of arrays is non-determinstic, so a recipe which mentions /dev/md0 could, in theory, match any of the arrays. No bueno.
Comment Actions
Change 608012 merged by Kormat:
[operations/puppet@production] install_server: Reuse partitions for dbprov* hosts
Comment Actions
As @jcrespo pointed out - we cannot currently test the dbprov reuse recipe, but the next time we're installing a new dbprov host we should test it then.
Comment Actions
Summary:
- tendril/zarcillo: not currently feasible, and not worth the effort repartitioning them to make it feasible.
- dbprov: done! (needs testing the next time a new dbprov host is imaged)
- backup: not feasiable. reuse-parts would need to know which physical disks belong to which mdraid devices, and the naming of those mdraid devices, which would be a huge amount of work for a tiny number of hosts that are almost never reimaged.
Comment Actions
dbprov recipe was tested yesterday successfully (https://gerrit.wikimedia.org/r/c/operations/puppet/+/618718 + T258749#6363993).