neutron/direct-physical-vnic-878d15bdb758b70e.yaml at 8718d5c2b6dd98e987185df7d6a5953ea8f1d34a - neutron - OpenDev: Free Software Needs Free Tools

openstack/neutron

Brent Eagles 2c60278992 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

2015-12-14 10:02:40 -03:30

7 lines

187 B

YAML

Raw Blame History

 ---
 prelude: >
     Add new VNIC type for SR-IOV physical functions.
 features:
   - Neutron now supports creation of ports for exposing physical functions
     as network devices to guests.