Add support for 'remote-managed' vnic type

The 'remote-managed' vnic type will be used to support off-path
SmartNIC port binding with OVN, and it is expected that the user
will create ports with this vnic type as part of the workflow.

As such the client must allow users to interact with this
vnic type and this patch addresses that.

Partial-Bug: #1932154
Depends-On: I496db96ea40da3bee5b81bcee1edc79e1f46b541
Change-Id: I566c3da594d757dd62edcf7f9ea3077db8d6b11a
This commit is contained in:
Frode Nordahl 2021-10-19 08:37:56 +02:00
parent e000fd5f0d
commit d565f11093
No known key found for this signature in database
GPG Key ID: 6A5D59A3BA48373F
2 changed files with 9 additions and 2 deletions

View File

@ -259,11 +259,12 @@ def _add_updatable_args(parser):
metavar='<vnic-type>',
choices=(
'direct', 'direct-physical', 'macvtap',
'normal', 'baremetal', 'virtio-forwarder', 'vdpa'
'normal', 'baremetal', 'virtio-forwarder', 'vdpa', 'remote-managed'
),
help=_(
"VNIC type for this port (direct | direct-physical | "
"macvtap | normal | baremetal | virtio-forwarder | vdpa, "
"macvtap | normal | baremetal | virtio-forwarder | vdpa | "
"remote-managed, "
"default: normal)"
),
)

View File

@ -0,0 +1,6 @@
---
features:
- |
Support for the ``remote-managed`` VNIC type has been added and can now be
passed to the ``--vnic-type`` option when used in conjunction with the
``port create`` and ``port set`` commands.