bc0870eade
There is a known limitation [1] and NICs that do not support SR-IOV require a different procedure [2] when configuring PCI-PT. This change adds a note on checking SR-IOV support for the target NIC, when configuring PCI-Passthrough for it, and adds the necessary steps for the configuration to work properly whit this type of NIC. For completeness, it also duplicates the PCI-PT example for when configuring PCI SRIOV Ethernet Interfaces, with the necessary changes to the procedure. [1] https://bugs.launchpad.net/starlingx/+bug/1836682 [2] https://wiki.openstack.org/wiki/StarlingX/Networking#Useful_Networking_Commands Partial-bug: 1836682 Signed-off-by: Thales Elero Cervi <thaleselero.cervi@windriver.com> Change-Id: I7258ab34cb7ce69a2f4b82c682f72d9467d95c70
171 lines
6.3 KiB
ReStructuredText
171 lines
6.3 KiB
ReStructuredText
|
|
.. vic1596720744539
|
|
.. _pci-sr-iov-ethernet-interface-devices:
|
|
|
|
===============================================
|
|
Configure PCI SR-IOV Ethernet Interface Devices
|
|
===============================================
|
|
|
|
A |SRIOV| ethernet interface is a physical |PCI| ethernet |NIC| that implements
|
|
hardware-based virtualization mechanisms to expose multiple virtual network
|
|
interfaces that can be used by one or more virtual machines simultaneously.
|
|
|
|
The |PCI|-SIG Single Root I/O Virtualization and Sharing \(|SRIOV|\) specification
|
|
defines a standardized mechanism to create individual virtual ethernet devices
|
|
from a single physical ethernet interface. For each exposed virtual ethernet
|
|
device, formally referred to as a Virtual Function \(VF\), the |SRIOV| interface
|
|
provides separate management memory space, work queues, interrupts resources,
|
|
and |DMA| streams, while utilizing common resources behind the host interface.
|
|
Each VF therefore has direct access to the hardware and can be considered to be
|
|
an independent ethernet interface.
|
|
|
|
When compared with a |PCI| Passthrough ethernet interface, a |SRIOV| ethernet
|
|
interface:
|
|
|
|
- Provides benefits similar to those of a |PCI| Passthrough ethernet interface,
|
|
including lower latency packet processing.
|
|
|
|
- Scales up more easily in a virtualized environment by providing multiple
|
|
VFs that can be attached to multiple virtual machine interfaces.
|
|
|
|
- Shares the same limitations, including the lack of support for |LAG|, |QoS|,
|
|
|ACL|, and live migration.
|
|
|
|
- Has the same requirements regarding the |VLAN| configuration of the access
|
|
switches.
|
|
|
|
- Provides a similar configuration workflow when used on |prod-os|.
|
|
|
|
|
|
The configuration of a |PCI| |SRIOV| ethernet interface is almost identical to
|
|
:ref:`Configure PCI Passthrough ethernet Interfaces
|
|
<configure-pci-passthrough-ethernet-interfaces>` and will be detailed bellow.
|
|
|
|
.. rubric:: |context|
|
|
|
|
|
|
Configure a |PCI| |SRIOV| on a host and request it for an
|
|
instance at boot/create time.
|
|
|
|
.. rubric:: |prereq|
|
|
|
|
.. note::
|
|
|
|
To use |PCI| passthrough or |SRIOV| devices, you must have Intel VT-x and
|
|
Intel VT-d features enabled in the BIOS.
|
|
|
|
The exercise assumes that the underlying data network **group0-data0** exists
|
|
already, and that |VLAN| ID 10 is a valid segmentation ID assigned to
|
|
**project1**.
|
|
|
|
.. rubric:: |proc|
|
|
|
|
#. Log in as the **admin** user to the |prod-p| |prod-hor-long|.
|
|
|
|
#. Lock the compute node you want to configure.
|
|
|
|
#. Configure the Ethernet interface to be used as a PCI passthrough interface.
|
|
|
|
|
|
#. Select **Admin** \> **Platform** \> **Host Inventory** from the left-hand pane.
|
|
|
|
#. Select the **Hosts** tab.
|
|
|
|
#. Click the name of the compute host.
|
|
|
|
#. Select the **Interfaces** tab.
|
|
|
|
#. Click the **Edit Interface** button associated with the interface you
|
|
want to configure.
|
|
|
|
|
|
The Edit Interface dialog appears.
|
|
|
|
.. image:: /node_management/figures/ptj1538163621290.png
|
|
|
|
Select **pci-sriov**, from the **Interface Class** drop-down, and
|
|
then select the data network to attach the interface.
|
|
|
|
You may also need to change the |MTU|.
|
|
|
|
The interface can also be configured from the |CLI| as illustrated below:
|
|
|
|
.. code-block:: none
|
|
|
|
~(keystone_admin)$ system host-if-modify -c pci-sriov compute-0 enp0s3
|
|
~(keystone_admin)$ system interface-datanetwork-assign compute-0 <enp0s3_interface_uuid> <group0_data0_data_network_uuid>
|
|
|
|
#. Create the **net0** project network
|
|
|
|
Log in as the **admin** user to the |os-prod-hor-long|.
|
|
|
|
Select **Admin** \> **Network** \> **Networks**, select the Networks tab, and then click **Create Network**. Fill in the Create Network dialog box as illustrated below. You must ensure that:
|
|
|
|
- **project1** has access to the project network, either assigning it as
|
|
the owner, as in the illustration \(using **Project**\), or by enabling
|
|
the shared flag.
|
|
|
|
- The segmentation ID is set to 10.
|
|
|
|
|
|
.. image:: /node_management/figures/bek1516655307871.png
|
|
|
|
The segmentation ID of the project network\(s\) used is more significant
|
|
here since this identifies the particular |VF| of the |SRIOV| interface
|
|
|
|
Click the **Next** button to proceed to the Subnet tab.
|
|
|
|
Click the **Next** button to proceed to the Subnet Details tab.
|
|
|
|
#. Configure the access switch. Refer to the OEM documentation to configure
|
|
the access switch.
|
|
|
|
Log in as the **admin** user to the |prod-p| |prod-hor-long|.
|
|
|
|
Configure the physical port on the access switch used to connect to
|
|
Ethernet interface **enp0s3** as an access port with default |VLAN| ID of 10.
|
|
Traffic across the connection is therefore untagged, and effectively
|
|
integrated into the targeted project network.
|
|
|
|
You can also use a trunk port on the access switch so that it handles
|
|
tagged packets as well. However, this opens the possibility for guest
|
|
applications to join other project networks using tagged packets with
|
|
different |VLAN| IDs, which might compromise the security of the system.
|
|
See |os-intro-doc|: :ref:`L2 Access Switches
|
|
<network-planning-l2-access-switches>` for other details regarding the
|
|
configuration of the access switch.
|
|
|
|
#. Unlock the compute node.
|
|
|
|
#. Create a neutron port with a |VNIC| type, direct-physical.
|
|
|
|
First, you must set up the environment and determine the correct
|
|
network |UUID| to use with the port.
|
|
|
|
.. code-block:: none
|
|
|
|
~(keystone_admin)$ source /etc/platform/openrc
|
|
~(keystone_admin)$ OS_AUTH_URL=http://keystone.openstack.svc.cluster.local/v3
|
|
~(keystone_admin)$ openstack network list | grep net0
|
|
~(keystone_admin)$ openstack port create --network <uuid_of_net0> --vnic-type direct <port_name>
|
|
|
|
You have now created a port to be used when launching the server in the
|
|
next step.
|
|
|
|
#. Launch the virtual machine
|
|
|
|
.. note::
|
|
|
|
You will need to source to the same project selected in the Create
|
|
Network 'net0' step.
|
|
|
|
- Specify the port uuid created
|
|
|
|
.. code-block:: none
|
|
|
|
~(keystone_admin)$ openstack server create --flavor <flavor_name> --image <image_name> --nic port-id=<port_uuid> <name>
|
|
|
|
For more information, see the Neutron documentation at:
|
|
`https://docs.openstack.org/neutron/train/admin/config-sriov.html
|
|
<https://docs.openstack.org/neutron/train/admin/config-sriov.html>`__.
|