587c3de89b
* This patch adds support for the virtio-forwarder VNIC type.
* The virtio-forwarder VNIC type has been added as another option for
setting the "binding:vnic_type" property on a port. This requests a
low-latency virtio port inside the instance, likely backed by hardware
acceleration.
* The documentation for OPENSTACK_NEUTRON_NETWORK/supported_vnic_types
has been updated to clarify the term "supported VNIC types".
Unfortunately, the VNIC binding happens at scheduling and error
reporting in core Nova and Neutron is not optimal in this case.
* Corresponding python-openstackclient change:
https://review.openstack.org/#/c/483532/
* Corresponding neutron-lib change:
https://review.openstack.org/#/c/483530/
Signed-off-by: Jan Gutter <jan.gutter@netronome.com>
Closes-Bug: 1705548
Depends-On: I28315fb12f62dc7d52d099c211086b2b81eca39a
Change-Id: I02dc3581de8f31c659e545e340cbdf6a1b2bb837
10 lines
499 B
YAML
10 lines
499 B
YAML
---
|
|
features:
|
|
- The ``virtio-forwarder`` VNIC type has been added to the list of valid
|
|
types that may be set on a port. This requests a low-latency virtio port
|
|
inside the instance, likely backed by hardware acceleration and requires a
|
|
supporting Neutron mechanism driver.
|
|
- The configuration documentation for ``supported_vnic_types`` in
|
|
``OPENSTACK_NEUTRON_NETWORK`` has been updated to help an operator decide
|
|
which VNIC types should be available for users to choose from.
|