yahoo-eng-team team mailing list archive

[OpenStack Infra <1527719@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/309904
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=fcdd1a9701a67ae992ba85d8c8c798fa22adbcaf
Submitter: Jenkins
Branch:    master

commit fcdd1a9701a67ae992ba85d8c8c798fa22adbcaf
Author: zhangguoqing <zhang.guoqing@xxxxxxxxxxx>
Date:   Mon Apr 25 17:15:30 2016 +0800

    Add description for new 'direct-physical' VNIC type.
    
    Change-Id: Ic549f5d35e8365a2a806cdaf6379043fd9817c7c
    Closes-Bug: #1527719


** Changed in: openstack-manuals
       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/1527719

Title:
      Adding a VNIC type for physical functions

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

Bug description:
  https://review.openstack.org/246923
  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 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

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