×

Before installing an OKD cluster that uses single-root I/O virtualization (SR-IOV) or Open vSwitch with the Data Plane Development Kit (OVS-DPDK) on OpenStack, review the requirements for each technology and complete all the preparatory tasks.

Requirements for clusters on OpenStack that use either SR-IOV or OVS-DPDK

If you use SR-IOV or OVS-DPDK with your deployment, you must meet certain requirements.

Ensure that OpenStack compute nodes use a flavor that supports huge pages.

Requirements for clusters on OpenStack that use SR-IOV

To use single-root I/O virtualization (SR-IOV) with your deployment, you must meet specific requirements.

The requirements are as follows:

  • You can plan your OpenStack SR-IOV deployment. See "Planning an SR-IOV deployment (OpenStack documentation)".

  • OKD must support the NICs that you use. For a list of supported NICs, see "About Single Root I/O Virtualization (SR-IOV) hardware networks".

  • For each node that will have an attached SR-IOV NIC, your OpenStack cluster must have:

    • One instance from the OpenStack quota

    • One port attached to the machines subnet

    • One port for each SR-IOV Virtual Function

    • A flavor with at least 16 GB memory, 4 vCPUs, and 25 GB storage space

  • SR-IOV deployments often employ performance optimizations, such as dedicated or isolated CPUs. For maximum performance, configure your underlying OpenStack deployment to use these optimizations, and then run OKD compute machines on the optimized infrastructure.

    • You can configure performant OpenStack compute nodes. See "Configuring the Compute Service for Instance Creation".

Requirements for clusters on OpenStack that use OVS-DPDK

To use Open vSwitch with the Data Plane Development Kit (OVS-DPDK) with your deployment, you must meet specific requirements.

  • Plan your OVS-DPDK deployment. For more information, see "Planning your OVS-DPDK deployment (OpenStack documentation)".

  • Configure your OVS-DPDK deployment. For more information, see "Configuring an OVS-DPDK deployment (OpenStack documentation)".

Creating SR-IOV networks for compute machines

If your OpenStack deployment supports single root I/O virtualization (SR-IOV), you can provision SR-IOV networks that compute machines run on.

You must configure your OpenStack platform before you install a cluster that uses SR-IOV on the platform.

The procedure uses an example of creating an external flat network and an external, VLAN-based network that can be attached to a compute machine. Depending on your OpenStack deployment, other network types might be required.

Prerequisites
  • Your cluster supports SR-IOV.

    If you are unsure about what your cluster supports, review the OKD SR-IOV hardware networks documentation.

  • You created radio and uplink provider networks as part of your OpenStack deployment. The names radio and uplink are used in all example commands to represent these networks.

Procedure
  1. On a command line, create a radio OpenStack network:

    $ openstack network create radio --provider-physical-network radio --provider-network-type flat --external
  2. Create an uplink OpenStack network:

    $ openstack network create uplink --provider-physical-network uplink --provider-network-type vlan --external
  3. Create a subnet for the radio network:

    $ openstack subnet create --network radio --subnet-range <radio_network_subnet_range> radio
  4. Create a subnet for the uplink network:

    $ openstack subnet create --network uplink --subnet-range <uplink_network_subnet_range> uplink

Preparing to install a cluster that uses OVS-DPDK

You must configure OpenStack before you install a cluster that uses OVS-DPDK on it.

After you perform preinstallation tasks, install your cluster by following the most relevant OKD on OpenStack installation instructions. You can then perform the tasks outlined in the additional resources section.

Procedure
  • Create a flavor and deploy an instance for OVS-DPDK before you install a cluster on OpenStack.

Next steps after completing preparatory tasks

After you completed preparatory configurations, you can complete additional tasks.

These additional tasks are listed as follows: