Chapter 3. Software requirements
This section describes the supported configurations and drivers, and subscription details necessary for NFV.
3.1. Registering and enabling repositories Copy linkLink copied to clipboard!
To install Red Hat OpenStack Platform, you must register Red Hat OpenStack Platform director using the Red Hat Subscription Manager, and subscribe to the required channels. For more information about registering and updating your undercloud, see Registering your system.
Procedure
Register your system with the Content Delivery Network, entering your Customer Portal user name and password when prompted.
sudo subscription-manager register
[stack@director ~]$ sudo subscription-manager register
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Determine the entitlement pool ID for Red Hat OpenStack Platform director, for example {Pool ID} from the following command and output:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Include the
Pool ID
value in the following command to attach the Red Hat OpenStack Platform 16.1 entitlement.sudo subscription-manager attach --pool={Pool-ID}-123456
[stack@director ~]$ sudo subscription-manager attach --pool={Pool-ID}-123456
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Disable the default repositories.
subscription-manager repos --disable=*
subscription-manager repos --disable=*
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Enable the required repositories for Red Hat OpenStack Platform with NFV.
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Update your system so you have the latest base system packages.
sudo dnf update -y sudo reboot
[stack@director ~]$ sudo dnf update -y [stack@director ~]$ sudo reboot
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
To register your overcloud nodes, see Ansible Based Registration.
3.2. Supported configurations for NFV deployments Copy linkLink copied to clipboard!
Red Hat OpenStack Platform (RHOSP) supports the following NFV deployments using director:
- Single root I/O virtualization (SR-IOV)
- Open vSwitch with Data Plane Development Kit (OVS-DPDK)
Additionally, you can deploy RHOSP with any of the following features:
RHOSP NFV deployments with Open Virtual Network (OVN) as the default Software Defined Networking (SDN) solution are unsupported. The following RHOSP NFV OVN configurations are generally available in RHOSP 16.1.4:
- OVN with OVS-DPDK colocated with SR-IOV
- OVN with OVS TC Flower offload
3.2.1. Deploying RHOSP with the OVS mechanism driver Copy linkLink copied to clipboard!
Deploy RHOSP with the OVS mechanism driver:
Procedure
Modify the
containers-prepare-parameter.yaml
file so that theneutron_driver
parameter is set toovs
.Copy to Clipboard Copied! Toggle word wrap Toggle overflow Include the
neutron-ovs.yaml
environment file in the/usr/share/openstack-tripleo-heat-templates/environments/services
directory with your deployment script.Copy to Clipboard Copied! Toggle word wrap Toggle overflow
3.2.2. Deploying OVN with OVS-DPDK and SR-IOV Copy linkLink copied to clipboard!
This RHOSP NFV OVN configuration is generally available in RHOSP 16.1.4.
Deploy DPDK and SRIOV VMs on the same node as OVN:
Procedure
Generate the
ComputeOvsDpdkSriov
role:openstack overcloud roles generate -o roles_data.yaml Controller ComputeOvsDpdkSriov
openstack overcloud roles generate -o roles_data.yaml Controller ComputeOvsDpdkSriov
Copy to Clipboard Copied! Toggle word wrap Toggle overflow -
Add
OS::TripleO::Services::OVNMetadataAgent
to the Controller role. Add the custom resources for OVS-DPDK with the
resource_registry
parameter:Copy to Clipboard Copied! Toggle word wrap Toggle overflow In the parameter_defaults section, edit the value of the tunnel type parameter to
geneve
:NeutronTunnelTypes: 'geneve' NeutronNetworkType: ['geneve', 'vlan']
NeutronTunnelTypes: 'geneve' NeutronNetworkType: ['geneve', 'vlan']
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Optional: If you use a centralized routing model, disable Distributed Virtual Routing (DVR):
NeutronEnableDVR: false
NeutronEnableDVR: false
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Under
parameters_defaults
, set the bridge mapping:The OVS logical-to-physical bridge mappings to use.
# The OVS logical-to-physical bridge mappings to use. NeutronBridgeMappings: "datacentre:br-ex,data1:br-link0,data2:br-link1"
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Configure the network interfaces in the
computeovsdpdksriov.yaml
file:Copy to Clipboard Copied! Toggle word wrap Toggle overflow Include the following yaml files in your deployment script:
- neutron-ovn-dpdk.yaml
- neutron-ovn-sriov.yaml
Open Virtual Networking (OVN) is the default networking mechanism driver in Red Hat OpenStack Platform 16.1. If you want to use OVN with distributed virtual routing (DVR), you must include the environments/services/neutron-ovn-dvr-ha.yaml
file in the openstack overcloud deploy
command. If you want to use OVN without DVR, you must include the environments/services/neutron-ovn-ha.yaml
file in the openstack overcloud deploy
command, and set the NeutronEnableDVR
parameter to false
. If you want to use OVN with SR-IOV, you must include the environments/services/neutron-ovn-sriov.yaml
file as the last of the OVN environment files in the openstack overcloud deploy
command.
3.2.3. Deploying OVN with OVS TC Flower offload Copy linkLink copied to clipboard!
Deploy OVS TC Flower offload on the same node as OVN.
This RHOSP NFV OVN configuration is generally available in RHOSP 16.1.4.
The Red Hat Enterprise Linux Traffic Control (TC) subsystem does not support connection tracking (conntrack) helpers or application layer gateways (ALGs). Therefore, if you are using ALGs, you must disable TC Flower offload.
Procedure
Generate the
ComputeOvsDpdkSriov
role:openstack overcloud roles generate -o roles_data.yaml ControllerSriov ComputeSriov
openstack overcloud roles generate -o roles_data.yaml ControllerSriov ComputeSriov
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Configure the
physical_network
parameter settings relevant to your deployment.-
For VLAN, set the
physical_network
parameter to the name of the network that you create in neutron after deployment. Use this value for theNeutronBridgeMappings
parameter also. Under role-specific parameters, such as
ComputeSriovOffloadParameters
, ensure the value of theOvsHwOffload
parameter istrue
.Copy to Clipboard Copied! Toggle word wrap Toggle overflow
-
For VLAN, set the
Configure the network interfaces in the
computeovsdpdksriov.yaml
file:Copy to Clipboard Copied! Toggle word wrap Toggle overflow Include the following yaml files in your deployment script:
- ovs-hw-offload.yaml
neutron-ovn-sriov.yaml
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
3.3. Supported drivers Copy linkLink copied to clipboard!
For a complete list of supported drivers, see Component, Plug-In, and Driver Support in Red Hat OpenStack Platform .
For a list of NICs tested for Red Hat OpenStack Platform deployments with NFV, see Tested NICs.
3.4. Compatibility with third-party software Copy linkLink copied to clipboard!
For a complete list of products and services tested, supported, and certified to perform with Red Hat OpenStack Platform, see Third Party Software compatible with Red Hat OpenStack Platform. You can filter the list by product version and software category.
For a complete list of products and services tested, supported, and certified to perform with Red Hat Enterprise Linux, see Third Party Software compatible with Red Hat Enterprise Linux. You can filter the list by product version and software category.