How do i configure tempest to use pre-configured ports so to test sriov

Asked by Kyle Fahrenthold

I have an openstack platform with sriov hardware offload support. I want to use tempest to test this functionality. I have looked through empest.conf and found the two network parameters, port_vnic_type and port_profile, to use for launching instances with pre-configured ports. How do I instruct tempest to use the pre-configured ports when creating Instances? I can't find any reference in the documentation on how this is done. Your help would be appreciated.

Thanks,

Kyle Fahrenthold

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu tempest Edit question
Assignee:
No assignee Edit question
Solved by:
Kyle Fahrenthold
Solved:
Last query:
Last reply:
Revision history for this message
Bernard Stafford (bernard010) said :
#1
Revision history for this message
Kyle Fahrenthold (kfahrenthold) said :
#2

Hello,

I have searched through all the documents you provided a link to and the only pre-configured port reference I can find is in the tempest.conf sample:

# vnic_type to use when launching instances with pre-configured ports.
# Supported ports are: ['normal', 'direct', 'macvtap', 'direct-
# physical', 'baremetal', 'virtio-forwarder'] (string value)
# Possible values:
# <None> - <No description provided>
# normal - <No description provided>
# direct - <No description provided>
# macvtap - <No description provided>
# direct-physical - <No description provided>
# baremetal - <No description provided>
# virtio-forwarder - <No description provided>
#port_vnic_type = <None>

# port profile to use when launching instances with pre-configured
# ports. (dict value)
#port_profile =

I have configure the two parameters as follows:

port_vnic_type = direct
port_profile = capabilities:[switchdev]

I can't find any reference how this works. How does tempest launch instances with pre-configured ports? I have run it many ways with no success.

Thanks,

Kyle

Revision history for this message
Bernard Stafford (bernard010) said (last edit ):
#3
Revision history for this message
Kyle Fahrenthold (kfahrenthold) said :
#4

I figured out that by adding the following two network parameters in the tempest.conf enables tempest to create ports with the correct vnic type and port profile required to support hardware offload.

port_vnic_type = direct
port_profile = capabilities:[switchdev]

I did observe that not all test in the network and compute category will create ports with the binding_vnic_type= direct which is what confused me in the beginning. Upon monitoring the system more closely during the tempest execution, tempest was launching Instances with the pre-configured ports containing binding_vnic_type= direct and binding_vnic_type= normal. I have successfully compiled a group of tests using the compute and network pattern to test this feature.