Server Lifecycle/DNS Transition

We are in the process of automating the generation of DNS records for the devices from Netbox data.

During the rollout phases of the new automation some procedure will change, as outlined below.

Phase 1

Transition of the management DNS records, both hostname and asset tag, to the Netbox-driven system.

Is the datacenter the device is in part of this list?

After having created the Netbox object(s) as usual for the new device(s):

No need to make a patch against the operations/dns repository to add the management IP/PTR (a patch is still needed to add primary IPv4/6).
Run the Create management interface Netbox script which creates a new management interface, allocates an IP address and configures it for automated DNS.
- To run the script in dry-run mode, uncheck the Commit changes checkbox.
Run the sre.dns.netbox cookbook as described.
- Ensure that the generated diff is consistent with your changes and there isn't any other change that seems unrelated. If in doubt feel free to ask Cas or Riccardo anytime.

Is the datacenter the device is in part of this list?

After having unracked the device:

No need to make a patch against operations/dns to the remove the management IP/PTR (a patch is still needed to remove the primary IPv4/6 if not already removed).
Run the Offline a device with extra actions Netbox script that will set the device in Offline status and delete all its interfaces and associated IP addresses left.
- To run the script in dry-run mode, uncheck the Commit changes checkbox.
Run the sre.dns.netbox cookbook as described.
- Ensure that the generated diff is consistent with your changes and there isn't any other change that seems unrelated. If in doubt feel free to ask Cas orRiccardo anytime.

Transition of the primary IPv4/6 DNS records to the Netbox-driven system.

Is the datacenter the device is in part of this list?

NO: nothing changes, follow usual procedure.
YES: follow the modified procedure described below for provisioning/decommissioning

[TBD]