openstack/neutron-lib
Code Issues Proposed changes

Add VNIC_REMOTE_MANAGED for off-path backends

Browse Source 
Added a new VNIC type for remote-managed ports of off-path networking
backends.

Related-Bug: #1932154
Change-Id: I496db96ea40da3bee5b81bcee1edc79e1f46b541
This commit is contained in:
Dmitrii Shcherbakov
2022-02-07 20:32:58 +03:00
committed by Frode Nordahl
parent c5fd7066f6
commit 18a6911720
3 changed files with 11 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
api-ref/source/v2/parameters.yaml
View File

@@ -2654,7 +2654,8 @@ binding:vnic_type:
The type of vNIC which this port should be attached to. This is used to The type of vNIC which this port should be attached to. This is used to
determine which mechanism driver(s) to be used to bind the port. determine which mechanism driver(s) to be used to bind the port.
The valid values are ``normal``, ``macvtap``, ``direct``, ``baremetal``, The valid values are ``normal``, ``macvtap``, ``direct``, ``baremetal``,
``direct-physical``, ``virtio-forwarder`` and ``smart-nic``. ``direct-physical``, ``virtio-forwarder``, ``smart-nic``
and ``remote-managed``.
What type of vNIC is actually available depends on deployments. What type of vNIC is actually available depends on deployments.
in: body in: body
required: true required: true
@@ -2664,7 +2665,8 @@ binding:vnic_type-request:
The type of vNIC which this port should be attached to. This is used to The type of vNIC which this port should be attached to. This is used to
determine which mechanism driver(s) to be used to bind the port. determine which mechanism driver(s) to be used to bind the port.
The valid values are ``normal``, ``macvtap``, ``direct``, ``baremetal``, The valid values are ``normal``, ``macvtap``, ``direct``, ``baremetal``,
``direct-physical``, ``virtio-forwarder`` and ``smart-nic``. ``direct-physical``, ``virtio-forwarder``, ``smart-nic``
and ``remote-managed``.
What type of vNIC is actually available depends on deployments. What type of vNIC is actually available depends on deployments.
The default is ``normal``. The default is ``normal``.
in: body in: body

3
neutron_lib/api/definitions/portbindings.py
View File

@@ -127,11 +127,12 @@ VNIC_VHOST_VDPA = 'vdpa'
# (https://wiki.openstack.org/wiki/Cyborg). # (https://wiki.openstack.org/wiki/Cyborg).
VNIC_ACCELERATOR_DIRECT = 'accelerator-direct' VNIC_ACCELERATOR_DIRECT = 'accelerator-direct'
VNIC_ACCELERATOR_DIRECT_PHYSICAL = 'accelerator-direct-physical' VNIC_ACCELERATOR_DIRECT_PHYSICAL = 'accelerator-direct-physical'
VNIC_REMOTE_MANAGED = 'remote-managed'
VNIC_TYPES = [VNIC_NORMAL, VNIC_DIRECT, VNIC_MACVTAP, VNIC_BAREMETAL, VNIC_TYPES = [VNIC_NORMAL, VNIC_DIRECT, VNIC_MACVTAP, VNIC_BAREMETAL,
VNIC_DIRECT_PHYSICAL, VNIC_VIRTIO_FORWARDER, VNIC_SMARTNIC, VNIC_DIRECT_PHYSICAL, VNIC_VIRTIO_FORWARDER, VNIC_SMARTNIC,
VNIC_VHOST_VDPA, VNIC_ACCELERATOR_DIRECT, VNIC_VHOST_VDPA, VNIC_ACCELERATOR_DIRECT,
VNIC_ACCELERATOR_DIRECT_PHYSICAL] VNIC_ACCELERATOR_DIRECT_PHYSICAL, VNIC_REMOTE_MANAGED]
# VIF_DETAILS_CONNECTIVITY: Indicates what kind of connectivity the network # VIF_DETAILS_CONNECTIVITY: Indicates what kind of connectivity the network
# back-end provides: L2, L3 or not specified. # back-end provides: L2, L3 or not specified.

5
releasenotes/notes/vnic-type-remote-managed-c0809926fcd30e93.yaml Normal file
View File

@@ -0,0 +1,5 @@
---
features:
- |
Add ``remote-managed`` VNIC type for ports such as off-path SmartNIC DPU
ports.