22c3ef8d65
This change fixes an issue that is most acute in test/dev environments but that may affect production environments as well: the presence of DHCP directories that no longer represent networks that exist in the Neutron DB. This issue can manifest itself over time if you delete networks from the Server while the Agent node is down. Without this fix, at the agent start-up the method existing_dhcp_networks will return an empty list, and as a consequence the directories that belong to networks that have been removed from the server will stay because the sync logic will not process them as it only looks at the mismatch between active networks on the agent and active networks on the server. With the fix instead, we return *all* existing dhcp networks; if they are meant to be active, the agent will bring them up, if they no longer exist on the server, then the agent will dispose of the resources. The dnsmasq driver will do the right thing when enabling or disabling the process. Fixes bug #1195770 Change-Id: I194064a449801713051d01193adc706bcb687c82
# -- 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 github at <http://github.com/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 http://docs.openstack.org/trunk/openstack-network/admin/content/
Neutron API Reference: http://docs.openstack.org/api/openstack-network/2.0/content/
The start of some developer documentation is available at: http://wiki.openstack.org/NeutronDevelopment
For help using or hacking on Neutron, you can send mail to <mailto:openstack-dev@lists.openstack.org>.