63cd4f5fdc
Incorporated patchset 1 review comments Updated patchset 5 review comments Updated patchset 6 review comments Fixed merge conflicts Updated patchset 8 review comments Change-Id: Icd7b08ab69273f6073b960a13cf59905532f851a Signed-off-by: Juanita-Balaraj <juanita.balaraj@windriver.com>
205 lines
6.8 KiB
ReStructuredText
205 lines
6.8 KiB
ReStructuredText
|
|
.. wjw1596720840345
|
|
.. _configure-pci-passthrough-ethernet-interfaces:
|
|
|
|
=============================================
|
|
Configure PCI Passthrough Ethernet Interfaces
|
|
=============================================
|
|
|
|
A passthrough Ethernet interface is a physical |PCI| Ethernet |NIC| on a compute
|
|
node to which a virtual machine is granted direct access. This minimizes packet
|
|
processing delays but at the same time demands special operational
|
|
considerations.
|
|
|
|
.. rubric:: |context|
|
|
|
|
You can specify interfaces when you launch an instance.
|
|
|
|
.. 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 |os-prod-hor| interface.
|
|
|
|
#. 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:: ../figures/ptj1538163621289.png
|
|
|
|
|
|
|
|
Select **pci-passthrough**, 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-passthrough compute-0 enp0s3
|
|
~(keystone_admin)$ system interface-datanetwork-assign compute-0 <enp0s3_interface_uuid> <group0_data0_data_network_uuid>
|
|
|
|
#. Create the **net0** project network
|
|
|
|
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:: ../figures/bek1516655307871.png
|
|
|
|
|
|
|
|
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.
|
|
|
|
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.
|
|
|
|
The neutron port can also be created from the |CLI|, using the following
|
|
command. 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-physical <port_name>
|
|
|
|
You have now created a port to be used when launching the server in the
|
|
next step.
|
|
|
|
#. Launch the virtual machine, specifying the port uuid created in *Step 7*.
|
|
|
|
.. note::
|
|
|
|
You will need to source to the same project selected in the Create
|
|
Network 'net0' in *step 4*.
|
|
|
|
.. 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>`__.
|
|
|
|
.. rubric:: |result|
|
|
|
|
The new virtual machine instance is up now. It has a PCI passthrough connection
|
|
to the **net0** project network identified with |VLAN| ID 10.
|
|
|
|
.. only:: partner
|
|
|
|
.. include:: ../../_includes/configuring-pci-passthrough-ethernet-interfaces.rest
|
|
|
|
:start-after: warning-text-begin
|
|
:end-before: warning-text-end
|
|
|
|
.. rubric:: |prereq|
|
|
|
|
Access switches must be properly configured to ensure that virtual machines
|
|
using |PCI|-passthrough or |SRIOV| Ethernet interfaces have the expected
|
|
connectivity. In a common scenario, the virtual machine using these interfaces
|
|
connects to external end points only, that is, it does not connect to other
|
|
virtual machines in the same |prod-os| cluster. In this case:
|
|
|
|
|
|
.. _configure-pci-passthrough-ethernet-interfaces-ul-pz2-w4w-rr:
|
|
|
|
- Traffic between the virtual machine and the access switch can be tagged or
|
|
untagged.
|
|
|
|
- The connecting port on the access switch is part of a port-based |VLAN|.
|
|
|
|
.. only:: partner
|
|
|
|
.. include:: ../../_includes/configuring-pci-passthrough-ethernet-interfaces.rest
|
|
|
|
:start-after: vlan-bullet-1-begin
|
|
:end-before: vlan-bullet-1-end
|
|
|
|
- The port-based |VLAN| provides the required connectivity to external
|
|
switching and routing equipment needed by guest applications to establish
|
|
connections to the intended end points.
|
|
|
|
|
|
For connectivity to other virtual machines in the |prod-os| cluster the
|
|
following configuration is also required:
|
|
|
|
|
|
.. _configure-pci-passthrough-ethernet-interfaces-ul-ngs-nvw-rr:
|
|
|
|
- The |VLAN| ID used for the project network, 10 in this example, and the
|
|
default port |VLAN| ID of the access port on the switch are the same. This
|
|
ensures that incoming traffic from the virtual machine is tagged internally by
|
|
the switch as belonging to |VLAN| ID 10, and switched to the appropriate exit
|
|
ports.
|
|
|
|
.. only:: partner
|
|
|
|
.. include:: ../../_includes/configuring-pci-passthrough-ethernet-interfaces.rest
|
|
|
|
:start-after: vlan-bullet-2-begin
|
|
:end-before: vlan-bullet-2-end
|
|
|
|
.. only:: partner
|
|
|
|
.. include:: ../../_includes/configuring-pci-passthrough-ethernet-interfaces.rest
|
|
|
|
:start-after: vlan-bullet-3-begin
|
|
:end-before: vlan-bullet-3-end
|
|
|
|
|
|
|