openstack
/
tempest
Code Issues Proposed changes

Allow additional port_vnic_type 

Also allow port_vnic_type direct-physical, baremetal and
virtio-forwarder.
Closes-Bug: #1905714

Change-Id: I31b18d1d815cafc8a327f611591fba84c6b5aeaf
This commit is contained in:
Tom Stappaerts 2020-11-26 12:07:47 +01:00
parent 6f50e7dc8b
commit 27fd5cb386
2 changed files with 12 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
tempest/config.py
View File

@ -757,11 +757,13 @@ NetworkGroup = [
deprecated_reason="This config option is no longer "
"used anywhere, so it can be removed."),
cfg.StrOpt('port_vnic_type',
choices=[None, 'normal', 'direct', 'macvtap'],
choices=[None, 'normal', 'direct', 'macvtap', 'direct-physical',
'baremetal', 'virtio-forwarder'],
help="vnic_type to use when launching instances"
" with pre-configured ports."
" Supported ports are:"
" ['normal','direct','macvtap']"),
" ['normal', 'direct', 'macvtap', 'direct-physical', "
"'baremetal', 'virtio-forwarder']"),
cfg.Opt('port_profile',
type=ProfileType,
default={},

8
tempest/scenario/manager.py
View File

@ -199,6 +199,14 @@ class ScenarioTest(tempest.test.BaseTestCase):
direct: an SR-IOV port that is directly attached to a VM
macvtap: an SR-IOV port that is attached to a VM via a macvtap
device.
direct-physical: an SR-IOV port that is directly attached to a
VM using physical instead of virtual
functions.
baremetal: a baremetal port directly attached to a baremetal
node.
virtio-forwarder: an SR-IOV port that is indirectly attached
to a VM using a low-latency vhost-user
forwarding process.
Defaults to ``CONF.network.port_vnic_type``.
* *port_profile* (``dict``) --
This attribute is a dictionary that can be used (with admin