This came up in conversation today with @ayounsi @Volans and @jbond . Now we're exporting mgmt hostnames for all network devices (i.e. hosts, switches, etc) from netbox to puppet hiera. This includes devices in decom'ing status, for which we currently don't generate DNS mgmt entries (only for the asset tag). This leads to export unresolvable mgmt hostnames in hiera, which I'd like to avoid (I'm using the data to instruct Prometheus to probe the mgmt interfaces).
My understanding is that:
- The hostname remains in netbox (i.e. still attached to the asset tag, even when in status decom'ing)
- Not having hostname mgmt DNS entries comes from the previous (i.e. non cookbook/netbox based) workflow
We'd like (please @ayounsi @Volans and @jbond correct/integrate at will) DC-Ops opinion on the matter, in particular whether leaving mgmt hostnames in DNS even for decom'ing hosts is something that will cause confusion (or some other breakage). On repurposing assets the hostname will change in netbox and conseguently DNS will match the new hostname when cookbooks run.
What do you think? Thank you!