ReleaseEngineering/How To/Decommission Slave: Difference between revisions
< ReleaseEngineering | How To
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 6: | Line 6: | ||
** Disable slave from production | ** Disable slave from production | ||
** Make sure is no longer attach to a master | ** Make sure is no longer attach to a master | ||
* Shut down machine | ** Shut down machine | ||
** Remove from Nagios | ** Remove from Nagios | ||
*** From puppet sysadmin repository (modules/nagios4/manifests/prod/releng/scl3.pp) | *** From puppet sysadmin repository (modules/nagios4/manifests/prod/releng/scl3.pp) |
Revision as of 07:27, 26 September 2017
There are a few steps that need to be followed here in order to decommission a slave.
The list of slaves in DB is available here (https://secure.pub.build.mozilla.org/slavealloc/ui/#slaves)
- In order to decommission a slave the bellow steps must be taken in this order:
- Disable slave from production
- Make sure is no longer attach to a master
- Shut down machine
- Remove from Nagios
- From puppet sysadmin repository (modules/nagios4/manifests/prod/releng/scl3.pp)
- Remove from Inventory
- People from DCOps team must mark these machines as decommissioned
- Remove from buildbot-configs
- mozilla-tests/production_config.py or mozilla/production_config.py
- Remove from DB
Usefull bug examples
- Bug 1396454
- Bug 1402830