decom sodium and shut it down
Description
Details
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • Cmjohnson | T110142 Decommission sodium | |||
| Resolved | akosiaris | T113828 move sodium backup to archive pool? |
Event Timeline
Change 239411 had a related patch set uploaded (by John F. Lewis):
remove sodium from puppet (spare/decom)
Decommission it means more than just merging that changeset; we have a process for that which also includes revocation of certificates, wiping the server etc.
eh, @faidon to get that one last backup i guess i have to re-add it to puppet for a moment, right :p
it's shutdown now.
it's also removed from puppet/icinga/salt.
this ticket should be complete after DNS removal, disk wiping and taking hardware out of rack or reclaim
We have an existing backup of /var/lib/mailman in bacula.
additionally i have /root , /etc/, /home , /usr/local and /var/log/mailman as .tar.gz files in my home on iron, which is backed up by bacula
Change 239414 had a related patch set uploaded (by Dzahn):
remove sodium.wm.o (leaving sodium.mgmt.eqiad.wmnet)
I did all the things on the Server Lifecycle page, site.pp , DHCP/netinstall, DNS but keep mgmt, puppet stored configs, puppet cert, salt key. confirmed backup in archive pool, etc up to "end steps" where we handover to the DC tech and have these remaining things:
*(decide if reclaim or final decom, purchase date 2011-01-27)
*Disable the production switch port.
*Wipe all disks on system
*Reset all system bios, mgmt bios, & raid bios settings to factory defaults.
*Unrack system & update Racktables, moving system from rack location to decommissioned rack....
and finally
*Once server is un-racked, remove its mgmt DNS entries.