6a37141f29
Closes-Bug: #1246080 Without this fix, if two or more compute hosts have instances which are sharing a given VLAN on a Nexus switch, and then all instances on one of the hosts which are using that VLAN are terminated, while instances which are using that VLAN on other hosts remain active, then the VLAN is not being untrunked from the corresponding interface on the Nexus switch as expected. This fix changes the VLAN removal logic from: ----If this the last instance using this VLAN on this switch: --------untrunk the vlan from the switch interface --------delete the VLAN from the switch To: ----If this the last instance using this VLAN on this switch interface: --------untrunk the vlan from the switch interface --------If this the last instance using this VLAN on this switch: ------------delete the VLAN from the switch Note that this bug also exists in the Cisco ML2 mechanism driver, but the code which implements this is being redesigned, so it will be addressed for the ML2 separately. Change-Id: Icb1f95d1db4baa56c0f6fd68ce6342bbff27641d
# -- 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>.