Reviewed: https://review.openstack.org/310927 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ea5fce2c91ae166fe2112ae4418940299d80ab13 Submitter: Jenkins Branch: master
commit ea5fce2c91ae166fe2112ae4418940299d80ab13 Author: Vladimir Eremin <[email protected]> Date: Thu Apr 28 15:14:18 2016 -0500 Fix SR-IOV binding when two NICs mapped to one physnet Because ESwitchManager._create_emb_switch stores one EmbSwitch per physnet, there is only last EmbSwitch works if two NICs was configured for one physnet: physical_device_mappings=physnet2:ens3f0,physnet2:ens3f1 This patch makes ESwitchManager.emb_switches_map store a list of EmbSwitch for physnet. Also fixed usage of singleton ESwitchManager class in tests by adding cleanup. Change-Id: I4fd9849890a770ea2b00063b546cc73a0f2d754c Closes-Bug: #1576757 ** Changed in: neutron Status: In Progress => 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/1576757 Title: SRIOV: ESwitchManager should handle multiple NICs per physical net Status in neutron: Fix Released Bug description: Commit 46ddaf4288a1cac44d8afc0525b4ecb3ae2186a3 made it possible to specify multiple NICs per network. However ESwitchManager now stores only one EmbSwitch per physical net (the last one). To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1576757/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
