]> review.fuel-infra Code Review - openstack-build/neutron-build.git/commit
Adding a VNIC type for physical functions
authorBrent Eagles <beagles@redhat.com>
Mon, 9 Nov 2015 12:56:53 +0000 (09:26 -0330)
committerBrent Eagles <beagles@redhat.com>
Mon, 14 Dec 2015 13:32:40 +0000 (10:02 -0330)
commit2c60278992d5a217241054444ed0ca6e1d2f3e5c
treeef31705d64e8fb1199be4682c7f6272bbe0e70f6
parent851464bbabd8eca3295256ca74f16d8b0b85a8b6
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
neutron/extensions/portbindings.py
neutron/plugins/ml2/drivers/mech_sriov/agent/sriov_nic_agent.py
neutron/plugins/ml2/drivers/mech_sriov/mech_driver/mech_driver.py
neutron/tests/unit/plugins/ml2/drivers/mech_sriov/agent/test_sriov_nic_agent.py
neutron/tests/unit/plugins/ml2/drivers/mech_sriov/mech_driver/test_mech_sriov_nic_switch.py
releasenotes/notes/direct-physical-vnic-878d15bdb758b70e.yaml [new file with mode: 0644]