This task will track the decommission-hardware of server db2057.codfw.wmnet
The first 5 steps should be completed by the service owner that is returning the server to DC-ops (for reclaim to spare or decommissioning, dependent on server configuration and age.)
db2057
Steps for service owner:
- - all system services confirmed offline from production use
- - set all icinga checks to maint mode/disabled while reclaim/decommmission takes place.
- - remove system from all lvs/pybal active configuration https://gerrit.wikimedia.org/r/#/c/529912/
- - any service group puppet/hiera/dsh config removed
- - remove site.pp, replace with role(spare::system) https://gerrit.wikimedia.org/r/#/c/529915/
- - unassign service owner from this task, check off completed steps, and assign to @RobH for followup on below steps.
Steps for DC-Ops:
The following steps cannot be interrupted, as it will leave the system in an unfinished state.
Start non-interrupt steps:
- - disable puppet on host
- - power down host
- - update netbox status to Inventory (if decom) or Planned (if spare)
- - disable switch port
- - switch port assignment noted on this task (for later removal)
- - remove all remaining puppet references (include role::spare)
- - remove production dns entries
- - puppet node clean, puppet node deactivate (handled by wmf-decommission-host)
- - remove dbmonitor entries on neodymium/sarin: sudo curl -X DELETE https://debmonitor.discovery.wmnet/hosts/${HOST_FQDN} --cert /etc/debmonitor/ssl/cert.pem --key /etc/debmonitor/ssl/server.key (handled by wmf-decommission-host)
End non-interrupt steps.
- - Label the controller as possibly broken so it doesn't get re-used T212275: db2057 storage crashed
- - system disks wiped (by onsite)
- - IF DECOM: system unracked and decommissioned (by onsite), update racktables with result
- - IF DECOM: add system to decommission tracking google sheet
- - IF DECOM: mgmt dns entries removed.