openstack-manuals patch:

This patch tries to close this bug, but the project does not match and as a 
result this bug is kept open.
Let's mark this as Invalid in neutron and mark it as Fix Released in 

** Also affects: openstack-manuals
   Importance: Undecided
       Status: New

** Changed in: openstack-manuals
       Status: New => Fix Released

** Changed in: neutron
       Status: Confirmed => Invalid

You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.

      Allow to use several nics for physnet with SR-IOV

Status in neutron:
Status in openstack-manuals:
  Fix Released

Bug description:
  Dear bug triager. This bug was created since a commit was marked with 
  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 aac460b0a7fec68fbb173ac8899274809e254a7a
  Author: Vladimir Eremin <>
  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)
      Change-Id: I07b8682fdfe8389a35893cc662b87c94a00bd4a5
      Closes-Bug: #1558626
      (cherry picked from commit 46ddaf4288a1cac44d8afc0525b4ecb3ae2186a3)

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to