Dane LeBlanc 9ceca26e11 Cisco nexus plugin fails to untrunk vlan if other hosts using vlan ... 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. Closes-Bug: #1246080 Change-Id: Icb1f95d1db4baa56c0f6fd68ce6342bbff27641d (cherry picked from commit a0a462f030)		2014-01-13 18:21:29 -05:00
..
n1kv	Add sub-type field to VXLAN network profiles for Cisco N1KV plugin	2013-09-05 10:59:51 -04:00
__init__.py	Rename Quantum to Neutron	2013-07-06 15:02:43 -04:00
test_network_db.py	Add support for the Nexus 1000V into the Cisco Plugin.	2013-08-09 16:56:54 -07:00
test_network_plugin.py	Cisco nexus plugin fails to untrunk vlan if other hosts using vlan	2014-01-13 18:21:29 -05:00
test_nexus_db.py	Adding VPC support to the Cisco plugin	2013-08-21 10:26:38 -04:00
test_nexus_plugin.py	Add clear_db to cleanup for TestCiscoNexusPlugin	2013-10-09 10:23:25 -04:00