ec2ad649ab
Instead of processing a port update notification directly in the RPC call, the actual processing is moved into the main rpc loop, whereas the RPC call just adds the updated port identifier to a set of updated ports. In this way, a port_update notification won't compete with the main rpc loop, causing long delays into its completion under heavy load. Also, repeated port_update notifications received within a single iteration of the main agent loop will be coalesced and processed only once. This will also avoid the risk of processing notifications out of order thus ending up with an actual configuration which differs from the desired one. This patch still performs L2 wiring for updated ports even if it is necessary only when the administrative state of a port changes. The update_ports method has been renamed to scan_ports as the latter name appears to be more in line with what the method actually does. Partial-Bug: #1253993 Partially implements blueprint: neutron-tempest-parallel Change-Id: I219c6bdf63b0b5e945b655677f9e28fa591f03cd
# -- 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>.