Blame docs/operations/decommission.md

1659c3
# Infra/node decommissioning
1659c3
1659c3
## High overview
1659c3
1659c3
This is an overview of the needed tasks to perform when we want to remove a node from our infra : 
1659c3
1659c3
  * Delete/reinstall the (virtual) machine (cleaning up)
1659c3
    * If hosted within Red Hat DC, update [internal ip inventory](https://docs.google.com/spreadsheets/d/1K-aewLJ17z3pRC6K5qyBRJYtNXy1WcxRSVwPkGf4NXQ) (Obviously need RH SSO and permission)
dc7015
  * Remove from [DNS](/infra/dns/) (public or internal, depending on the case and don't forget to also remove from PowerDNS if record is delegated to that dns infra, see below)
1659c3
  * Remove it from Ansible inventory (and search for references for that node in case of)
1659c3
  * Remove it from Zabbix monitoring
410a52
  * (optional and if sponsored : remove sponsor logo from [website git repo](https://git.centos.org/centos/centos.org) )
1659c3
410a52
Worth knowing that if node is used in one of the [mirror,mirror.stream,vault,debuginfo] roles, it needs to be also removed from the sqlite DB used to generate the dynamic powerdns setup.
1659c3
90e422
```
90e422
host="centost8.centos.org"
90e422
pushd /var/lib/centos-infra/
90e422
echo "delete from nodes where fqdn='${host}';" | sqlite3 nodes.db
90e422
./gen_backend
90e422
popd
90e422
```