2541ff7cad
Plugging a device usually involves checking for the existence of the device twice, once before calling plug and once after. It turns out that these calls are expensive, often taking a half second or more each. For that reason, it is worth the effort to make sure we check only once. The device driver is now responsible for cleanly plugging/unplugging the device without knowing whether it exists or not. Pushing this responsibility to the device driver allows implementing it more efficiently in terms of calls made out to the operating system. This is targetted at the neutron-tempest-parallel bp because it shaves time off the time to set up a router, something that hinders parallel performance. Change-Id: I391fafe68b76e1c620d2b25e8613ba507fd25dfd Partial-Bug: #1287824
# -- 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>.