yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #20032
[Bug 1288393] Re: Nexus ML2 mechanism driver need to specify multiple interfaces per host
** Changed in: neutron
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1288393
Title:
Nexus ML2 mechanism driver need to specify multiple interfaces per
host
Status in OpenStack Neutron (virtual network service):
Fix Released
Bug description:
There are some L2 topologies in which traffic from a physical server
can come into multiple interfaces on the ToR switch configured by the
Nexus plugin. In the case of server directly attached to ToR, this is
easily taken care of by by port-channel/bonding. However, if an
intermediary device (e.g. Cisco UCS Fabric Interconnect) is placed
between the server and the Top of Rack switch, then server traffic has
the possibility of coming into multiple interfaces on the same switch.
So the user needs to be able to specify multiple interfaces per host.
Currently the plugin stores the information in a dictionary defined like this:
device_dictionary[dev_id, dev_ip, dev_key] = value[0]
In this setup, specifying a second interface would just overwrite the
first. We need to either make the dictionary key include the
interface, or make the value of the current dictionary key a list
instead of single item.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1288393/+subscriptions
References