Decommissioning Servers
From Wikitech
(Difference between revisions)
| Line 8: | Line 8: | ||
* Add the server to the decommissioning puppet manifest & update puppet. (Currently only removes the server from Nagios.) | * Add the server to the decommissioning puppet manifest & update puppet. (Currently only removes the server from Nagios.) | ||
* Remove the certificate for the server off sockpuppet. | * Remove the certificate for the server off sockpuppet. | ||
| + | * Wipe data off server. | ||
| + | * Move the server to decomissioned racks in racktables. | ||
Revision as of 18:23, 9 May 2011
Currently the process for decommissioning servers is under a state of flux. Things are being updated to make this process more standardized and streamlined.
- Check/Update/Remove server from Server_roles : This is becoming very outdated, but should be updated and checked on servers removed.
- If database server, ensure it is not online in any cluster and that mysql services are not running (or slaved to another server, or providing the master server for others to replicate.)
- If apache, ensure it is not a memcached server.
- Remove from LVS pybal configuration(s).
- Remove from DSH node lists.
- Add the server to the decommissioning puppet manifest & update puppet. (Currently only removes the server from Nagios.)
- Remove the certificate for the server off sockpuppet.
- Wipe data off server.
- Move the server to decomissioned racks in racktables.
