003091a974
patch 0de1d8d4c introduced a new behavior whereby dnsmasq can rely on dns resolvers defined in the host's resolv.conf, and it did that by default. However this may introduce dns timeouts if the dns servers are not reachable for whatever reason. This may be especially likely in certain gate configurations (where the VM under test is a guest itself). Regardless of the root-cause analysis, this option should have defaulted to False to preserve backward compatibility, therefore this patch restores the old behavior in a way that local DNS resolution occurs only if the new option variable is set to True, or the admin has not explicitly set the list of DNS servers to be injected in the DHCP response. DocImpact: document how to configure DNS resolution by dnsmasq Change-Id: I90ab26bfa83c2d23c92110b8da73ef771e11f7bb
Welcome!
You have come across a cloud computing network fabric controller. It has identified itself as "Neutron." It aims to tame your (cloud) networking!
External Resources:
The homepage for Neutron is: http://launchpad.net/neutron. Use this site for asking for help, and filing bugs. Code is available on git.openstack.org at <http://git.openstack.org/cgit/openstack/neutron>.
The latest and most in-depth documentation on how to use Neutron is available at: <http://docs.openstack.org>. This includes:
- Neutron Administrator Guide
- Networking Guide
- Neutron API Reference:
-
http://docs.openstack.org/api/openstack-network/2.0/content/
- Current Neutron developer documentation is available at:
For help on usage and hacking of Neutron, please send mail to <mailto:openstack-dev@lists.openstack.org>.
For information on how to contribute to Neutron, please see the contents of the CONTRIBUTING.rst file.