openstack
/
neutron-lib
Code Issues Proposed changes

Merge "Add smartnic port type to VNIC_TYPES"

This commit is contained in:
Zuul 2019-01-16 22:59:06 +00:00 committed by Gerrit Code Review
parent 4e1bc16c2f f3f220ed62
commit 98764984c9
3 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -1980,7 +1980,7 @@ binding:vnic_type:
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.
The valid values are ``normal``, ``macvtap``, ``direct``, ``baremetal``,
``direct-physical`` and ``virtio-forwarder``.
``direct-physical``, ``virtio-forwarder`` and ``smart-nic``.
What type of vNIC is actually available depends on deployments.
in: body
required: true
@ -1990,7 +1990,7 @@ binding:vnic_type-request:
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.
The valid values are ``normal``, ``macvtap``, ``direct``, ``baremetal``,
``direct-physical`` and ``virtio-forwarder``.
``direct-physical``, ``virtio-forwarder`` and ``smart-nic``.
What type of vNIC is actually available depends on deployments.
The default is ``normal``.
in: body

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

@ -112,9 +112,10 @@ VNIC_MACVTAP = 'macvtap'
VNIC_BAREMETAL = 'baremetal'
VNIC_DIRECT_PHYSICAL = 'direct-physical'
VNIC_VIRTIO_FORWARDER = 'virtio-forwarder'
VNIC_SMARTNIC = 'smart-nic'
VNIC_TYPES = [VNIC_NORMAL, VNIC_DIRECT, VNIC_MACVTAP, VNIC_BAREMETAL,
VNIC_DIRECT_PHYSICAL, VNIC_VIRTIO_FORWARDER]
VNIC_DIRECT_PHYSICAL, VNIC_VIRTIO_FORWARDER, VNIC_SMARTNIC]
# The alias of the extension.

4
releasenotes/notes/vnic-type-smart-nic-45dd5a22a9d1aa63.yaml Normal file
View File

@ -0,0 +1,4 @@
---
features:
- |
Add ``smart-nic`` VNIC type for Smart NIC ports.