Driver is not naming VLANs on switch

Bug #1602808 reported by James Denton
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-cisco
New
Undecided
Unassigned

Bug Description

Using Cisco Nexus mechanism driver 3.2 in a Mitaka environment.

The driver does not name VLANs on the switch as one would expect. The commit that introduced this change can be seen here:

http://git.openstack.org/cgit/openstack/networking-cisco/commit/networking_cisco/plugins/ml2/drivers/cisco/nexus/nexus_network_driver.py?id=6df65927938b27e014042e4bebb3381a02ec19b5

One of the key changes mentions:

- Eliminate vlan name. Instead just create all the vlan based on port binding configuration.

If the VLAN name is being indeed being eliminated, there is a lot of cleanup that could be done, including removing the following two configuration options:

vlan_name_prefix
provider_vlan_name_prefix

Did naming VLANs on the switch (a one-time operation at time of creation) really result in significant time savings? VLAN name are a good thing to administrators who need to identify VLANs on a switch.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.