Questo contenuto non è disponibile nella lingua selezionata.

Chapter 2. Preparing to install a cluster that uses SR-IOV or OVS-DPDK on OpenStack


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

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

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

2.1.1. Requirements for clusters on RHOSP or RHOSO 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:

  • If you use Red Hat OpenStack Platform (RHOSP), see "Planning an SR-IOV deployment (Red Hat OpenStack Platform (RHOSP) documentation)".
  • If you use Red Hat OpenStack Services on OpenShift (RHOSO), see "Planning an SR-IOV deployment (Red Hat OpenStack Services on OpenShift (RHOSO) documentation)".
  • OpenShift Container Platform 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 RHOSP cluster must have:

    • One instance from the 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 RHOSP deployment to use these optimizations, and then run OpenShift Container Platform compute machines on the optimized infrastructure.

    • If you use RHOSP, see "Configuring CPUs on Compute nodes (Red Hat OpenStack Platform (RHOSP) documentation)".
    • If you use RHOSO, see "NFV performance considerations (Red Hat OpenStack Services on OpenShift (RHOSO) documentation)".

2.1.2. Requirements for clusters on RHOSP or RHOSO that use OVS-DPDK

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

The requirements are as follows:

  • If you use Red Hat OpenStack Platform (RHOSP):

    • Plan your OVS-DPDK deployment. For more information, see "Planning your OVS-DPDK deployment (Red Hat OpenStack Platform (RHOSP) documentation)".
    • Configure your OVS-DPDK deployment. For more information, see "Configuring an OVS-DPDK deployment (Red Hat OpenStack Platform (RHOSP) documentation)".
  • If you use Red Hat OpenStack Services on OpenShift (RHOSO):

    • Plan your OVS-DPDK deployment. For more information, see "Planning an OVS-DPDK deployment (Red Hat OpenStack Services on OpenShift (RHOSO) documentation)".
    • Configure your OVS-DPDK deployment. For more information, see"Creating the data plane for SR-IOV and DPDK environments (Red Hat OpenStack Services on OpenShift (RHOSO) documentation)".

2.2. Creating SR-IOV networks for compute machines

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

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

Note

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 RHOSP deployment, other network types might be required.

Prerequisites

  • Your cluster supports SR-IOV.

    Note

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

  • You created radio and uplink provider networks as part of your RHOSP 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 RHOSP network:

    $ openstack network create radio --provider-physical-network radio --provider-network-type flat --external
  2. Create an uplink RHOSP 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

2.3. Preparing to install a cluster that uses OVS-DPDK

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

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

Procedure

  • Depending on your platform, complete one of the following tasks:

    • If you use Red Hat OpenStack Platform (RHOSP), create a flavor and deploy an instance for OVS-DPDK before you install a cluster on RHOSP.
    • If you use Red Hat OpenStack Services on OpenShift (RHOSO), create a custom OVS-DPDK compute service before you install a cluster on RHOSO.

2.4. Next steps after completing preparatory tasks

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

These additional tasks are listed as follows:

Red Hat logoGithubredditYoutubeTwitter

Formazione

Prova, acquista e vendi

Community

Informazioni su Red Hat

Forniamo soluzioni consolidate che rendono più semplice per le aziende lavorare su piattaforme e ambienti diversi, dal datacenter centrale all'edge della rete.

Rendiamo l’open source più inclusivo

Red Hat si impegna a sostituire il linguaggio problematico nel codice, nella documentazione e nelle proprietà web. Per maggiori dettagli, visita il Blog di Red Hat.

Informazioni sulla documentazione di Red Hat

Legal Notice

Theme

© 2026 Red Hat
Torna in cima