Add smartnic port type to VNIC_TYPES

Neutron OVS ML2 mechanism driver will allow binding the `smart-nic`
vnic_type. The rationale for creating new vnic_type and not using the
barmetal one is that there is a wide range of mechanism drivers that
use heirachical port binding for configuring TOR switches and we want
to allow this to work with smart NICs.

Story: #2003346
Change-Id: I91f63810626ce4e054e358f5de5e46434c4da131
This commit is contained in:
Hamdy Khader 2018-12-12 12:49:43 +02:00
parent 152342413b
commit f3f220ed62
3 changed files with 8 additions and 3 deletions

View File

@ -1926,7 +1926,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
@ -1936,7 +1936,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

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.

View File

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