
routers_updated does not acquire any lock just updates a set for future rpc loop processing. The self.updated_routers can be changed by concurrent update notification. If this change happens at the time around the self.plugin_rpc.get_routers call, the additional routers - by mistake - is considered as admin_state_up=false routers, which are safe to delete. Creating a local copy of the updated_routers and preserve the fresh updated_routers entries for the next _rpc_loop operations. Change-Id: Icc7377f9c29e248c3b34562465e859b15ecc2ec3 Closes-Bug: #1315467 Partial-Bug: #1253896
# -- 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>.