Addressed in networking guide by https://github.com/openstack/openstack- manuals/commit/fd09293551b2c29b2f47a10ab9c14446f76dd85c
** Changed in: openstack-manuals Status: Confirmed => 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/1564125 Title: Allow to use several nics for physnet with SR-IOV Status in neutron: Invalid Status in openstack-manuals: Fix Released Bug description: https://review.openstack.org/294188 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to. commit 46ddaf4288a1cac44d8afc0525b4ecb3ae2186a3 Author: Vladimir Eremin <vere...@mirantis.com> Date: Thu Mar 17 19:32:29 2016 +0300 Allow to use several nics for physnet with SR-IOV Accordind specs and docs, SRIOV_NIC.physical_device_mappings is not limited to be a 1-1 mapping between physnets and NICs. However, implementation requires this. This bugfix unlocks 1-M mappings, so one physnet could be managed by many NICs. * introduced unique_keys in neutron.utils.parse_mappings * SRIOV_NIC.physical_device_mappings is parsed as dict with lists as values with parse_mappings(..., unique_keys=False) DocImpact Change-Id: I07b8682fdfe8389a35893cc662b87c94a00bd4a5 Closes-Bug: #1558626 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1564125/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp