[openstack-dev] [nova] Providing interface-scoped nameservers in network_data.json

Lars Kellogg-Stedman lars at redhat.com
Mon Jun 5 17:27:34 UTC 2017

While investigating a bug report against cloud-init ("why don't you put
nameservers in interface configuration files?"). I discovered that Nova
munges the information received from Neutron to take the network-scoped
nameserver entries and move them all into a global "services" section.

It turns out that people may actually want to preserve the information
about which interface is associated with a particular nameserver so that
the system can be configured to manage the resolver configuration as
interfaces are brought up/down.

I've proposed https://review.openstack.org/#/c/467699/ to resolve this
issue, which adds nameserver information to the "network" section.  This
*does not* remove the global "services" key, so existing code that expects
to find nameservers there will continue to operate as it does now.  This
simply exposes the information in an additional location where there is
more context available.

Thanks for looking,

-- Lars
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170605/748cdd59/attachment.html>

More information about the OpenStack-dev mailing list