an-test-coord1002

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. (likely done by script)
• - remove system from all lvs/pybal active configuration
• - any service group puppet/hiera/dsh config removed
• - remove site.pp, replace with role(spare::system) recommended to ensure services offline but not 100% required as long as the decom script is IMMEDIATELY run below.
• - login to cumin host and run the decom cookbook: cookbook sre.hosts.decommission <host fqdn> -t <phab task>. This does: bootloader wipe, host power down, netbox update to decommissioning status, puppet node clean, puppet node deactivate, debmonitor removal, and run homer.
• - remove all remaining puppet references and all host entries in the puppet repo
• - reassign task from service owner to DC ops team member and site project (ops-sitename) depending on site of server

End service owner steps / Begin DC-Ops team steps:

• - system disks removed (by onsite)
• - determine system age, under 5 years are reclaimed to spare, over 5 years are decommissioned.
• - IF DECOM: system unracked and decommissioned (by onsite), update netbox with result and set state to offline
• - IF DECOM: mgmt dns entries removed.

Original description below

The server an-test-coord1002 was intended to be used for T280905: Analytics coordinator failover improvements.

It was requisitioned from spares in T289784 and the ticket T287864: Deploy an-test-coord1002 to facilitate failover testing of analytics coordinator role was intended to be used to track the work.

However, in almost two years we have not found the time to take the project forward and now an-test-coord1002 is due to be decommissioned.

I think it is therfore best to proceed with decommissioning this server. We can still look at other means of improving availability as part of the T302728: Analytics Platform Future State Planing

This task will track the decommission-hardware of server <enter FQDN of server here>.

With the launch of updates to the decom cookbook, the majority of these steps can be handled by the service owners directly. The DC Ops team only gets involved once the system has been fully removed from service and powered down by the decommission cookbook.