This page contains historical information. The transition has been completed.

2020

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.

Automation Rollout Phase summary

Task / Phase	1 [done]	2 [done]	3	4
Select and Assign MGMT IP	Netbox CustomScript	Netbox CustomScript	Netbox CustomScript	Netbox CustomScript
Deploy MGMT DNS records	Manual	Cookbook	Cookbook	Cookbook
Select and Assign Primary IPv4/6	Manual	Manual	Netbox CustomScript	Netbox CustomScript
Deploy Primary IPv4/6 DNS records	Manual	Manual	Manual	Cookbook

IP Assignment for servers

The status pre-migration is that every IP assignment is done manually by looking for an unused IP in the DNS repository.

Phase 1 (COMPLETED 2020-06-24)

Transition of all servers management IP assignment from manual to automatically assigned by Netbox via the run of a custom script, independently of the datacenter they are physically in.

At the moment of the migration a sync of all existing management IP addresses with related DNS name from the DNS repository to Netbox will be re-run, making the two set of data identical. After that moment every modification to management IP addresses must be done in Netbox as the sole source of truth for them.

Provisioning

Run the Add interfaces and IPs to devices 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.

Phase 3 (COMPLETED: 2020-09-14)

Transition of all primary IPv4 and IPv6 assignment from manual to automatically assigned by Netbox via the run of a custom script, independently of the datacenter they are physically in.

At the moment of the migration a sync of all existing interfaces, IP addresses and related DNS names from PuppetDB and the DNS repository to Netbox will be re-run, making the two set of data identical. After that moment every modification to host IP addresses must be done in Netbox as the sole source of truth for them.

Provisioning

Run the Add interfaces and IPs to devices Netbox script, which creates a new management interface, allocates an IP address and configures it for automated DNS. It will also create a ##PRIMARY## interface, allocates an IPv4 and a mapped IPv6 and configures it for automated DNS. The automated DNS for the IPv6 can be opted out. The primary interface name will be updated by the reimage procedure with the real interfaces on the host.
- To run the script in dry-run mode, uncheck the Commit changes checkbox.

DNS records

The status pre-migration is that every DNS record is manually hardcoded in the operations/dns repository.

Phase 2 (COMPLETED)

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

Provisioning

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

~~NO: nothing changes, follow usual procedure to make the operations/dns repository patch.~~
YES: follow the modified procedure described below.

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 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.

Unracking

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. This step must be performed in all cases.
- To run the script in dry-run mode, uncheck the Commit changes checkbox.

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

~~NO: nothing else changes, follow usual procedure for the DNS patch.~~
YES: follow the modified procedure described below.

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 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.

Phase 4 (COMPLETED: 2020-11-24)

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

After running either the Add interfaces and IPs to devices or the Offline a device with extra actions Netbox scripts, 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?

NO: an additional manual patch to the DNS repository is still needed to propagate the DNS changes
YES: nothing else to do