yahoo-eng-team team mailing list archive

[OpenStack Infra <1500993@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/246923
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=2c60278992d5a217241054444ed0ca6e1d2f3e5c
Submitter: Jenkins
Branch:    master

commit 2c60278992d5a217241054444ed0ca6e1d2f3e5c
Author: Brent Eagles <beagles@xxxxxxxxxx>
Date:   Mon Nov 9 09:26:53 2015 -0330

    Adding a VNIC type for physical functions
    
    This change adds a new VNIC type to distinguish between virtual and
    physical functions in SR-IOV.
    
    The new VNIC type 'direct-physical' deviates from the behavior of
    'direct' VNICs for virtual functions. While neutron tracks the resource
    as a port, it does not currently perform any management functions.
    Future changes may extend the segment mapping functionality that is
    currently based on agent configuration to include direct types.
    However, the direct-physical VNICs will not have functional parity with
    the other SR-IOV VNIC types in that quality of service and port security
    functionality is not available.
    
    APIImpact
    DocImpact: Add description for new 'direct-physical' VNIC type.
    
    Closes-Bug: #1500993
    
    Change-Id: If1ab969c2002c649a3d51635ca2765c262e2d37f


** 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/1500993

Title:
  Missing vNIC type for SR-IOV physical functions

Status in neutron:
  Fix Released

Bug description:
  One of the telco working group requirements is being able to expose a
  whole PF (physical function) on an SR-IOV card.

  To indicate that to nova, we need to specify we want a
  "physicalfunction" type of port.

  It's different from the ironic baremetal ports in the sense that those
  PFs will be memory mapped to the guest.

  nova spec: https://review.openstack.org/#/c/212472/

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1500993/+subscriptions