0de1d8d4ca
It's pointless to not include default DNS resolution for Neutron. This adds a new config option (dnsmasq_local_resolv) which defaults to 'True' and will allow for DNS name resolution to work out of the box. The caveat is that if the 'dnsmasq_dns_servers' is set it will override the 'dnsmasq_local_resolv' setting, thus allowing operators to explicitly set their own DNS servers. DocImpact: Default to using local DNS resolution with the DHCP agent. Change-Id: I17a884f467d307432a06f67a9dd93ed2fa6081a3 Closes-Bug: #1466117 Signed-off-by: Kyle Mestery <mestery@mestery.com> |
||
---|---|---|
.. | ||
.placeholder | ||
add-availability-zone-4440cf00be7c54ba.yaml | ||
config-file-generation-2eafc6602d57178e.yaml | ||
default-local-dns-a1c3fa1451f228fa.yaml | ||
deprecate-router_id-34aca9ea5ee9e789.yaml | ||
deprecated-driver-e368e0befc9bee4c.yaml | ||
direct-physical-vnic-878d15bdb758b70e.yaml | ||
hyperv-neutron-agent-decomposition-ae6a052aeb48c6ac.yaml | ||
oslo-reports-166a169037bf64f2.yaml | ||
rm-notify-entry-points-aa442134a780469a.yaml | ||
use-keystoneauth-24f309566001a16b.yaml |