ML2 Nexus MD does not appear to configure multiple switches

Bug #1331857 reported by Robert Starmer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Medium
Nader Lahouti

Bug Description

There is already a bug to add unit tests for multi-switch configuration, but there already appears to be a bug in that multiple switches can be defined in the configuration file, but multiple switches are not configured. The related bug is here:

https://bugs.launchpad.net/neutron/+bug/1330598

The issue is:

If you configure the Cisco Nexus ML2 MD with two switches that have the same target hypervisor ID, as in:

[ml2_mech_cisco_nexus_1:1.1.1.1]
compute-1=1/2

[ml2_mech_cisco_nexus_2:1.1.1.2]
compute-1=1/2

The system will only configure a VLAN on interface 1/2 on ml2_mech_cisco_nexus_1.

In addition it appears that the system will only ever configure devices on the first switch that is discovered.

Also, it does not appear possible to define port-channels as the target for these configurations, which breaks the use of virtual port-channel as a configured mechanism.

Tags: cisco ml2
tags: added: cisco ml2
Changed in neutron:
importance: Undecided → High
status: New → Confirmed
Shiv Haris (shh)
Changed in neutron:
assignee: nobody → nlahouti (nlahouti)
Revision history for this message
Rich Curran (rcurran) wrote :

The multi-switch support was added in Juno-1 via https://bugs.launchpad.net/neutron/+bug/1294900
Review: https://review.openstack.org/#/c/83546/

Rich Curran (rcurran)
Changed in neutron:
status: Confirmed → Fix Released
Shiv Haris (shh)
Changed in neutron:
importance: High → Medium
milestone: none → juno-3
Thierry Carrez (ttx)
Changed in neutron:
milestone: juno-3 → 2014.2
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.