Fully decom/wipe amssq31-62 in esams (32 hosts). Doubtful they'll be reclaimed/reused, they're rather old and of weak config.
Description
Details
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | wiki_willy | T235805 ESAMS Refresh/Rebuild (October 2019) | |||
Resolved | faidon | T184061 SRE 2017-18 Q3 goal Cleanup esams and refresh servers and infrastructure (tracking) | |||
Resolved | Papaul | T184063 Remove all decommissioned hardware | |||
Resolved | mark | T95742 Decomission amssq31-62 (32 hosts) |
Event Timeline
Done so far:
- Removed from puppet/pybal cache pools/definitions
- Removed from site.pp
- puppeted once without any specific role
- shredded private keys (for whatever that's worth...)
- disabled puppet clients
- shutdown with poweroff
- on palladium: cleaned puppet certs, salt keys, puppet storedconfig
Change 213965 had a related patch set uploaded (by Dzahn):
remove amssq31-62 incl. mgmt
Change 213966 had a related patch set uploaded (by Dzahn):
remove amss31-62 from DHCP
Change 213968 had a related patch set uploaded (by Dzahn):
torrus: remove amssq nodes from tests/cdn.pp
Change 213969 had a related patch set uploaded (by Dzahn):
rolematcher: remove amssq nodes
Aside from the 4 tickets above to clean out the puppet+dns repos, I think the only thing we're really missing from the Server Lifecycle doc here is disable/unlabel of switch ports and opening a hw ticket for physical decom work on future esams site visit.
Switch work done (also disabled/unconfigured the old amslvs1-4 ports, missed back when those were decommed)
Yes, I'll remove these in the near future - likely before we refresh the other (newer) low range cp* hosts.