Red Hat SummitQuesto contenuto non è disponibile nella lingua selezionata.
Chapter 3. Install OpenDaylight on the overcloud
This document focuses only on OpenDaylight installation. Before you can deploy OpenDaylight, you must ensure that you have a working undercloud environment and that the overcloud nodes are connected to the physical network.
See Installing the Undercloud and Configuring Basic Overcloud Requirements with the CLI Tools of the Director Installation and Usage guide, which describes the procedures necessary to deploy the undercloud and overcloud.
There are several methods to install OpenDaylight in Red Hat OpenStack platform. The following chapter introduces the most useful scenarios of OpenDaylight and how to install them.
3.1. Understand default configuration and customizing settings
The recommended approach to installing OpenDaylight is to use the default environment file neutron-opendaylight.yaml and pass it as an argument to the deployment command on the undercloud. This deploys the default installation of OpenDaylight.
Other OpenDaylight installation and configuration scenarios are based on this installation method. You can deploy OpenDaylight with various different scenarios by providing specific environment files to the deployment command.
3.1.1. Understanding the default environment file
The default environment file is neutron-opendaylight.yaml in the /usr/share/openstack-tripleo-heat-templates/environments/services directory. This environment file enables or disables services that the OpenDaylight supports. The environment file also defines necessary parameters that the director sets during deployment.
The following file is an example neutron-opendaylight.yaml file that you can use for a Docker based deployment:
Red Hat OpenStack Platform director uses the resource_registry to map resources for a deployment to the corresponding resource definition yaml file. Services are one type of resource that you can map. If you want to disable a particular service, set the value OS::Heat::None. In the default file, the OpenDaylightApi and OpenDaylightOvs services are enabled, while default neutron agents are explicitly disabled as OpenDaylight inherits their functionality.
You can use heat parameters to configure settings for a deployment with director. You can override their default values with the parameter_defaults section of the environment file.
In this example, the NeutronEnableForceMetadata, NeutronMechanismDrivers, and NeutronServicePlugins parameters are set to enable OpenDaylight.
The list of other services and their configuration options are provided later in this guide.
3.1.2. Configuring the OpenDaylight API Service
You can change the default values in the /usr/share/openstack-tripleo-heat-templates/puppet/services/opendaylight-api.yaml file to suit your needs. Do not overwrite the settings in this file directly. Duplicate this file and retain the original as a backup solution. Only modify the duplicate and pass the duplicate to the deployment command.
The parameters in the latter environment files override those set in previous environment files. Ensure that you pay attention to the order of the environment files to avoid overwriting parameters accidentally.
3.1.2.1. Configurable Options
When you configure the OpenDaylight API Service, you can set several parameters:
|
|
The port used for Northbound communication. The default value is |
|
|
The login user name for OpenDaylight. The default value is |
|
|
The login password for OpenDaylight. The default value is |
|
|
Enables OpenDaylight to act as the DHCP service. The default value is |
|
|
A comma-delimited list of features to boot in OpenDaylight. The default value is |
|
|
The L7 protocol used for REST access. The default value is |
|
|
Defines whether to manage the OpenDaylight repository. The default value is |
|
|
The SNAT mechanism to be used by OpenDaylight. Select |
|
|
The logging mechanism for OpenDaylight. Select |
|
|
The password for the OpenDaylight TLS keystore. The default value is |
|
|
Enables or disables TLS in the internal network. You can use values |
|
|
If you enable TLS for services in the internal network, you must use the |
For more information on how to deploy with TLS, see the Advanced Overcloud Customization Guide.
3.1.3. Configuring the OpenDaylight OVS Service
You can change the default values in the /usr/share/openstack-tripleo-heat-templates/puppet/services/opendaylight-ovs.yaml file to suit your needs. Do not overwrite the settings in this file directly. Duplicate this file and retain the original as a backup solution. Modify only the duplicate and pass the duplicate to the deployment command.
The parameters in the latter environment files override those set in previous environment files. Ensure that you pay attention to the order of the environment files to avoid overwriting parameters accidentally.
3.1.3.1. Configurable options
When you configure the OpenDaylight OVS Service, you can set several parameters:
|
|
The port used for Northbound communication to OpenDaylight. The default value is |
|
|
The Layer 7 protocol used for REST access. The default value is |
|
|
The URL to verify OpenDaylight is fully up before OVS connects. The default value is |
|
|
A comma-delimited list of mappings between logical networks and physical interfaces. This setting is required for VLAN deployments. The default value is |
|
|
The custom username for the OpenDaylight OVS service. The default value is |
|
|
The custom password for the OpenDaylight OVS service. The default value is |
|
|
Defines the allowed tenant network types for this OVS host. They can vary per host or role to constrain the hosts that nova instances and networks are scheduled to. The default value is |
|
|
Enable or disable DPDK in OVS. The default values is |
|
|
The mode for OVS with vhostuser port creation. In client mode, the hypervisor is responsible for creating vhostuser sockets. In server mode, OVS creates them. The default value is |
|
|
The directory to use for vhostuser sockets. The default value is |
|
|
Enables or disables OVS Hardware Offload. You can use |
|
|
Enables or disables TLS in the internal network. You can use values |
|
|
If you enable TLS for services in the internal network, you must use the |
|
|
The OpenDaylight update level. You can use values |
|
|
The vhost-user socket directory group. When vhostuser is in the default |
|
|
The vhost-user socket directory user name. When vhostuser is in the default |
3.1.4. Using neutron metadata service with OpenDaylight
The OpenStack Compute service allows virtual machines to query metadata associated with them by making a web request to a special address, 169.254.169.254. The OpenStack Networking proxies such requests to the nova-api, even when the requests come from isolated or multiple networks with overlapping IP addresses.
The Metadata service uses either the neutron L3 agent router to serve the metadata requests or the DHCP agent instance. Deploying OpenDaylight with the Layer 3 routing plug-in enabled disables the neutron L3 agent. Therefore Metadata must be configured to flow through the DHCP instance, even when a router exists in a tenant network. This functionality is enabled in the default environment file neutron-opendaylight.yaml. To disable it, set the NeutronEnableForceMetadata to false.
VM instances have a static host route installed, using the DHCP option 121, for 169.254.169.254/32. With this static route in place, Metadata requests to 169.254.169.254:80 go to the Metadata name server proxy in the DHCP network namespace. The namespace proxy then adds the HTTP headers with the instance’s IP to the request, and connects it to the Metadata agent through the Unix domain socket. The Metadata agent queries neutron for the instance ID that corresponds to the source IP and the network ID and proxies it to the nova Metadata service. The additional HTTP headers are required to maintain isolation between tenants and allow overlapping IP support.
3.1.5. Understanding the network configuration and NIC template
In Red Hat OpenStack Platform director, the physical neutron network datacenter is mapped to an OVS bridge called br-ex by default. It is consistently the same with the OpenDaylight integration. If you use the default OpenDaylightProviderMappings and plan to create a flat or VLAN _External network, you have to configure the OVS br-ex bridge in the NIC template for Compute nodes. Since the Layer 3 plug-in uses distributed routing to these nodes, it is not necessary to configure br-ex on the Controller role NIC template any more.
The br-ex bridge can be mapped to any network in network isolation, but it is typically mapped to the External network, as shown in the example.
With the DPDK, you must create another OVS bridge, typically called br-phy, and provide it with the ovs-dpdk-port. The IP address of the bridge is configured for VXLAN overlay network tunnels.
When using network isolation, you do not need to place an IP address, or a default route, in this bridge on Compute nodes.
Alternatively, you can configure external network access without using the br-ex bridge. To use this method, you must know the interface name of the overcloud Compute node in advance. For example, if eth3 is the deterministic name of the third interface on the Compute node, then you can use it to specify an interface in the NIC template for the Compute node.
- type: interface name: eth3 use_dhcp: false
-
type: interface
name: eth3
use_dhcp: false3.2. Basic installation of OpenDaylight
This section shows how to deploy OpenDaylight with the standard environment files.
3.2.1. Prepare the OpenDaylight environment files for overcloud
Before you start
- Install the undercloud. For more information, see Installing the undercloud.
- Optionally, create a local registry with the container images that you want to use during the overcloud and OpenDaylight installation. For more information, see Configuring a container image source in the Director installation and usage guide.
Procedure
Log in to the undercloud and load the admin credentials.
source ~/stackrc
$ source ~/stackrcCopy to Clipboard Copied! Toggle word wrap Toggle overflow Create a Docker registry file
odl-images.yamlthat contains references to the Docker container images that you need for the OpenStack and OpenDaylight installation.openstack overcloud container image prepare -e /usr/share/openstack-tripleo-heat-templates/environments/services-docker/neutron-opendaylight.yaml --output-env-file /home/stack/templates/odl-images.yaml
$ openstack overcloud container image prepare -e /usr/share/openstack-tripleo-heat-templates/environments/services-docker/neutron-opendaylight.yaml --output-env-file /home/stack/templates/odl-images.yamlCopy to Clipboard Copied! Toggle word wrap Toggle overflow
You now successfully prepared the environment to deploy overcloud and you are ready to start the installation described in Section 3.2.2, “Install overcloud with OpenDaylight”.
More information
The openstack overcloud image prepare command prepares the container images environment files for the installation of overcloud and OpenDaylight. This command uses the following options:
- -e
- specifies the service environment file to add specific container images required by that environment, such as OpenDaylight and OVS
- --env-file
- creates a new container image environment file with a list of container images to use for the installation
- --pull-source
- sets the location of the Docker containers registry
- --namespace
- sets the version of the Docker containers
- --prefix
- adds a prefix to the image name
- --suffix
- adds a suffix to the image name
- --tag
- defines the release of the images
3.2.2. Install overcloud with OpenDaylight
Before you start
- Follow the Prepare the OpenDaylight environment files for overcloud procedure to create the necessary environment files for the deployment.
Procedure
Log in to the undercloud and load the admin credentials.
source ~/stackrc
$ source ~/stackrcCopy to Clipboard Copied! Toggle word wrap Toggle overflow Deploy the overcloud using previously created environment files.
openstack overcloud deploy --templates /usr/share/openstack-tripleo-heat-templates \ -e <other environment files>
$ openstack overcloud deploy --templates /usr/share/openstack-tripleo-heat-templates \ -e <other environment files> -e /usr/share/openstack-tripleo-heat-templates/environments/services-docker/neutron-opendaylight.yaml \ -e /home/stack/templates/odl-images.yamlCopy to Clipboard Copied! Toggle word wrap Toggle overflow
Environment files present in the deployment command overwrite environment files that you include earlier in the command. You must pay attention to the order of the environment files that you include to avoid overwriting parameters accidentally.
You can override some of the parameters by creating a minimal environment file that sets only the parameters that you want to change and combining it with the default environment files.
More information
The openstack overcloud deploy command in this procedure uses the following options:
- --templates
- defines the path to the heat templates directory
- -e
- specifies an environment file
3.3. Install OpenDaylight in custom role
Installing OpenDaylight in a Custom role results in an isolated OpenDaylightApi service that runs on a designated OpenDaylight node, different from the Controller node.
If you want to use a Custom role for OpenDaylight, you must create a role file that contains node layout and function configuration.
3.3.1. Customize the role file based on default roles
You can deploy OpenStack with a user-defined list of roles, each role running a user-defined list of services. A role is a group of nodes that contains individual services or configurations. For example, you can create a Controller role that contains the nova API service. You can view example roles in openstack-tripleo-heat-templates.
Use these roles to generate a roles_data.yaml file that contains the roles that you want for the overcloud nodes. You can also create custom roles by creating individual files in a directory and use them to generate a new roles_data.yaml.
To create customized environment files that install only specific OpenStack roles, complete the following steps:
Procedure
Load the admin credentials.
source ~/stackrc
$ source ~/stackrcCopy to Clipboard Copied! Toggle word wrap Toggle overflow List the default roles that you can use to generate the custom
roles_data.yamlfile.openstack overcloud role list
$ openstack overcloud role listCopy to Clipboard Copied! Toggle word wrap Toggle overflow If you want to use all of these roles, run the following command to generate a
roles_data.yamlfile:openstack overcloud roles generate -o roles_data.yaml
$ openstack overcloud roles generate -o roles_data.yamlCopy to Clipboard Copied! Toggle word wrap Toggle overflow If you want to customize the role file to include only some of the roles, you can pass the names of the roles as arguments to the command in the previous step. For example, to create a
roles_data.yamlfile with the Controller, Compute and Telemetry roles, run the following command:openstack overcloud roles generate - roles_data.yaml Controller Compute Telemetry
$ openstack overcloud roles generate - roles_data.yaml Controller Compute TelemetryCopy to Clipboard Copied! Toggle word wrap Toggle overflow
3.3.2. Create a custom role for OpenDaylight
To create a custom role, create a new role file in the role files directory and generate a new roles_data.yaml file. For each custom role that you create, you must create a new role file. Each custom role file must include the data only for a specific role, and the custom role file name must match the role name.
Minimally, the file must define these parameters:
Name:defines the name of the role. The name must always be a non-empty unique string.- Name: Custom_role
- Name: Custom_roleCopy to Clipboard Copied! Toggle word wrap Toggle overflow ServicesDefault:lists the services used in this role. The variable can remain empty, if there are no services used. The example format looks like this:Copy to Clipboard Copied! Toggle word wrap Toggle overflow
In addition to the required parameters, you can also define further settings:
CountDefault:defines the default number of nodes. IfCountDefault:is empty, it defaults to zero.CountDefault: 1
CountDefault: 1Copy to Clipboard Copied! Toggle word wrap Toggle overflow HostnameFormatDefault:defines the format string for a host name. The value is optional.HostnameFormatDefault: '%stackname%-computeovsdpdk-%index%'
HostnameFormatDefault: '%stackname%-computeovsdpdk-%index%'Copy to Clipboard Copied! Toggle word wrap Toggle overflow Description:describes and adds information about the role.Description: Compute OvS DPDK RoleDescription: Compute OvS DPDK RoleCopy to Clipboard Copied! Toggle word wrap Toggle overflow
Procedure
Copy the default role files into a new directory and keep the original files as a backup.
mkdir ~/roles cp /usr/share/openstack-tripleo-heat-templates/roles/* ~/roles
$ mkdir ~/roles $ cp /usr/share/openstack-tripleo-heat-templates/roles/* ~/rolesCopy to Clipboard Copied! Toggle word wrap Toggle overflow Modify the default Controller role in the
Controller.yamlfile in~/rolesand remove theOpenDaylightApiline from the file to disable the OpenDaylightAPI service on the Controller node:Copy to Clipboard Copied! Toggle word wrap Toggle overflow Create a new
OpenDaylight.yamlfile in the~/rolesdirectory and add the OpenDaylight role description:Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Save the file.
Generate the new role file to use when you deploy the OpenStack overcloud with OpenDaylight in the custom role.
openstack overcloud roles generate --roles-path ~/roles -o ~/roles_data.yaml Controller Compute OpenDaylight
$ openstack overcloud roles generate --roles-path ~/roles -o ~/roles_data.yaml Controller Compute OpenDaylightCopy to Clipboard Copied! Toggle word wrap Toggle overflow
3.3.3. Install OverCloud with OpenDaylight in the custom role
Before you start
- Install the undercloud. For more information, see Installing the undercloud.
- Create environment files with links to overcloud container images. For more information, see Preparing the installation of overcloud with OpenDaylight.
- Prepare the role file to configure OpenDaylight in a custom role. For more information, see Create a custom role for OpenDaylight.
Procedure
Create a custom role. Set the following parameter values in the environment file:
- OvercloudOpenDaylightFlavor: opendaylight - OvercloudOpenDaylightCount: 3- OvercloudOpenDaylightFlavor: opendaylight - OvercloudOpenDaylightCount: 3Copy to Clipboard Copied! Toggle word wrap Toggle overflow For more information, see Creating a roles_data file.
Run the deployment command with the -r argument to override the default role definitions. This option tells the deployment command to use the
roles_data.yamlfile that contains your custom role. Pass theodl-composable.yamlenvironment file that you created in the previous step to this deployment command. In this example, there are three ironic nodes in total. One ironic node is reserved for the custom OpenDaylight role:Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Environment files present in the deployment command overwrite environment files that you include earlier in the command. You must pay attention to the order of the environment files that you include to avoid overwriting parameters accidentally.
You can override some of the parameters by creating a minimal environment file that sets only the parameters that you want to change and combining it with the default environment files.
More information
The
-roption overrides the role definitions at installation time.-r <roles_data>.yaml
-r <roles_data>.yamlCopy to Clipboard Copied! Toggle word wrap Toggle overflow - A custom role requires an extra ironic node during the installation.
- To override the node counter in the rhosp13 composable role for any custom role, use the syntax in this example: <role-name>Count: <value> The role name updates with accurate name details from role_data.yaml file.
3.3.4. Verify the installation of OpenDaylight in custom role
Before you start
- Install the Overcloud with OpenDaylight in the custom role. For more information, see Install Overcloud with OpenDaylight in custom role.
Procedure
List the existing instances:
openstack server list
$ openstack server listCopy to Clipboard Copied! Toggle word wrap Toggle overflow Verify that the new OpenDaylight role is dedicated as an instance:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
3.4. Install OpenDaylight with SR-IOV support
OpenDaylight might be deployed with Compute nodes that support Single Root Input/Output Virtualization (SR-IOV). In this deployment, Compute nodes must operate as dedicated SR-IOV nodes and must not be mixed with nova instances based on OVS. It is possible to deploy both OVS and SR-IOV Compute nodes in a single OpenDaylight deployment.
This scenario utilizes a custom SR-IOV Compute role to accomplish this kind of deployment.
The SR-IOV deployment requires that you use the neutron SR-IOV agent to configure the virtual functions (VFs). These functions are then passed to the Compute instance directly when it is deployed, and they serve as a network port. The VFs derive from a host NIC on the Compute node, and therefore some information about the host interface is required before you start the deployment.
3.4.1. Prepare the SR-IOV Compute role
Following the same methodology as shown in Install of OpenDaylight In Custom Role, you must create a custom role for the SR-IOV Compute nodes to allow creation of the SR-IOV based instances, while the default Compute role serves the OVS based nova instances.
Before you start
- Study the chapter Install of OpenDaylight In Custom Role
Procedure
Copy the default role files into a new directory and keep the original files as a backup.
mkdir ~/roles cp /usr/share/openstack-tripleo-heat-templates/roles/* ~/roles
$ mkdir ~/roles $ cp /usr/share/openstack-tripleo-heat-templates/roles/* ~/rolesCopy to Clipboard Copied! Toggle word wrap Toggle overflow Create a new
ComputeSriov.yamlfile in the~/rolesdirectory and add the following role description:Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Save the file.
Remove the
NeutronSriovAgentandNeutronSriovHostConfigservices from the default Compute role and save the information in roles_data.yaml.- OS::TripleO::Services::NeutronSriovHostConfig - OS::TripleO::Services::NeutronSriovAgent- OS::TripleO::Services::NeutronSriovHostConfig - OS::TripleO::Services::NeutronSriovAgentCopy to Clipboard Copied! Toggle word wrap Toggle overflow Generate the new role file to use to deploy the OpenStack overcloud with OpenDaylight Compute SR-IOV support.
openstack overcloud roles generate --roles-path ~/roles -o ~/roles_data.yaml Controller Compute ComputeSriov
$ openstack overcloud roles generate --roles-path ~/roles -o ~/roles_data.yaml Controller Compute ComputeSriovCopy to Clipboard Copied! Toggle word wrap Toggle overflow Create the local registry:
openstack overcloud container image prepare --namespace=192.168.24.1:8787/rhosp13 --prefix=openstack- --tag=2018-05-07.2 -e /home/stack/templates/environments/services-docker/neutron-opendaylight.yaml -e /home/stack/templates/environments/services-docker/neutron-opendaylight-sriov.yaml --output-env-file=/home/stack/templates/overcloud_images.yaml --roles-file /home/stack/templates/roles_data.yaml
openstack overcloud container image prepare --namespace=192.168.24.1:8787/rhosp13 --prefix=openstack- --tag=2018-05-07.2 -e /home/stack/templates/environments/services-docker/neutron-opendaylight.yaml -e /home/stack/templates/environments/services-docker/neutron-opendaylight-sriov.yaml --output-env-file=/home/stack/templates/overcloud_images.yaml --roles-file /home/stack/templates/roles_data.yamlCopy to Clipboard Copied! Toggle word wrap Toggle overflow
3.4.2. Configuring the SR-IOV agent service
To deploy OpenDaylight with the SR-IOV support, you must override the default parameters in the neutron-opendaylight.yaml file. You can use a standard SR-IOV environment file that resides in /usr/share/openstack-tripleo-heat-templates and the neutron-opendaylight.yaml environment file. However, it is a good practice not to edit the original files. Instead, duplicate the original environment file and modify the parameters in the duplicate file.
Alternatively, you can create a new environment file in which you provide only the parameters that you want to change, and use both files for deployment. To deploy the customized OpenDaylight, pass both files to the deployment command. Because newer environment files override any previous settings, you must include them in the deployment command in the correct order. The correct order is neutron-opendaylight.yaml first, and then neutron-opendaylight-sriov.yaml.
If you want to deploy OpenDaylight and SR-IOV with the default settings, you can use the neutron-opendaylight-sriov.yaml that is provided by Red Hat. If you need to change or add parameters, make a copy of the default SR-IOV environment file and edit the newly created file.
The following is an illustrative example of a customized neutron-opendaylight-sriov.yaml file:
More information
You can configure the following options in the neutron-opendaylight-sriov.yaml file. The table describes individual options and mentions the required settings to enable the SR-IOV functionality:
|
|
Allows the use of PCI Passthrough for SR-IOV. This must be uncommented in the environment file and include |
|
|
Enables specifying PCI Passthrough Filter for Nova Default filters. Must be set and include |
|
| Maps the logical neutron network to a host network interface. This must be specified so that neutron is able to bind the virtual network to a physical port. |
|
|
Number of VFs to create for a host network interface. Syntax: |
|
| Configures the whitelist of allowed PCI devices in nova to be used for PCI Passthrough in a list format, for example: NovaPCIPassthrough:
- vendor_id: "8086"
product_id: "154c"
address: "0000:05:00.0"
physical_network: "datacentre"
It can also simply use logical device name rather than specific hardware attributes: NovaPCIPassthrough:
- devname: "ens20f2"
physical_network: "datacentre"
|
3.4.3. Install OpenDaylight with SR-IOV
Before you start
- Install the undercloud. For more information, see Installing the undercloud.
- Create environment files with links to overcloud container images. For more information, see Preparing the installation of overcloud with OpenDaylight).
- Prepare the role file to configure OpenDaylight in a custom role with the SR-IOV support. For more information, see Prepare the SR-IOV compute role.
Procedure
Run the deployment command with the
-rargument to include your custom role file and the necessary environment files to enable the SR-IOV functionality with OpenDaylight.Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Environment files present in the deployment command overwrite environment files that you include earlier in the command. You must pay attention to the order of the environment files that you include to avoid overwriting parameters accidentally.
You can override some of the parameters by creating a minimal environment file that sets only the parameters that you want to change and combining it with the default environment files.
More information
The
-roption overrides the role definitions at installation time.-r <roles_data>.yaml
-r <roles_data>.yamlCopy to Clipboard Copied! Toggle word wrap Toggle overflow - A custom role requires an extra ironic node during the installation.
3.5. Install OpenDaylight with OVS-DPDK support
OpenDaylight might be deployed with Open vSwitch Data Plane Development Kit (DPDK) acceleration with director. This deployment offers higher dataplane performance as packets are processed in user space rather than in the kernel. Deploying with OVS-DPDK requires knowledge of the hardware physical layout for each Compute node to take advantage of potential performance gains.
You should consider especially:
- that the network interface on the host supports DPDK
- the NUMA node topology of the Compute node (number of sockets, CPU cores, and memory per socket)
- that the DPDK NIC PCI bus proximity to each NUMA node
- the amount of RAM available on the Compute node
- consulting the Network Functions Virtualization Planning and Configuration Guide.
3.5.1. Prepare the OVS-DPDK deployment files
To deploy OVS-DPDK, use a different environment file. The file will override some of the parameters set by the neutron-opendaylight.yaml environment file in the /usr/share/openstack-tripleo-heat-templates/environments/services-docker directory. Do not modify the original environment file. Instead, create a new environment file that contains the necessary parameters, for example neutron-opendaylight-dpdk.yaml.
If you want to deploy OpenDaylight with OVS-DPDK with the default settings, use the default neutron-opendaylight-dpdk.yaml environment file in the /usr/share/openstack-tripleo-heat-templates/environments/services-docker directory.
The default file contains the following values:
3.5.2. Configuring the OVS-DPDK deployment
You can configure the OVS-DPDK service by changing the values in neutron-opendaylight-dpdk.yaml.
|
|
Enables pinning of IRQs in order to isolate them from the CPU cores to be used with OVS-DPDK. Default profile: |
|
|
Specifies a list of CPU cores to prevent the kernel scheduler from using these cores that can instead be assigned and dedicated to OVS-DPDK. The format takes a comma separated list of individual or a range of cores, for example |
|
|
Lists arguments to be passed to the kernel at boot time. For OVS-DPDK, it is required to enable
---- Note the amount of RAM for specified is 60 GB for hugepages. It is important to consider the available amount of RAM on Compute nodes when setting this value. |
|
| Specifies the amount of hugepage memory (in MB) to assign to each NUMA node. For maximum performance, assign memory to the socket closest to the DPDK NIC. List format of memory per socket: ---- "<socket 0 mem MB>,<socket 1 mem MB>" ---- For example: "1024,0" |
|
|
Specifies the UIO driver type to use with PMD threads. The DPDK NIC must support the driver specified. Red Hat OpenStack Platform deployments support the driver type |
|
|
Lists single cores or ranges of cores for PMD threads to be pinned to. The cores specified here should be on the same NUMA node where memory was assigned with the |
|
| Specifies the number of memory channels per socket. |
|
| Cores to pin nova instances to with libvirtd. For best performance use cores on the same socket where OVS PMD Cores have been pinned to. |
3.5.3. Install OpenDaylight with OVS-DPDK
Before you start
- Install the undercloud. For more information, see Installing the undercloud.
- Create environment files with links to overcloud container images. For more information, see Preparing the installation of overcloud with OpenDaylight.
- Prepare the role file to configure OpenDaylight in a custom role with the SR-IOV support. For more information, see Prepare the OVS-DPDK deployment files.
Procedure
- Run the deployment command with the necessary environment files to enable the DPDK functionality with OpenDaylight.
Environment files present in the deployment command overwrite environment files that you include earlier in the command. You must pay attention to the order of the environment files that you include to avoid overwriting parameters accidentally.
You can override some of the parameters by creating a minimal environment file that sets only the parameters that you want to change and combining it with the default environment files.
3.5.4. Example: Configuring OVS-DPDK with ODL and VXLAN tunnelling
This section describes an example configuration of OVS-DPDK with ODL and VXLAN tunnelling.
You must determine the best values for the OVS-DPDK parameters that you set in the network-environment.yaml file to optimize your OpenStack network for OVS-DPDK. See Deriving DPDK parameters with workflows for details.
3.5.4.1. Generating the ComputeOvsDpdk composable role
Generate roles_data.yaml for the ComputeOvsDpdk role.
openstack overcloud roles generate --roles-path templates/openstack-tripleo-heat-templates/roles -o roles_data.yaml Controller ComputeOvsDpdk
# openstack overcloud roles generate --roles-path templates/openstack-tripleo-heat-templates/roles -o roles_data.yaml Controller ComputeOvsDpdk3.5.4.2. Configuring OVS-DPDK parameters
You must determine the best values for the OVS-DPDK parameters that you set in the network-environment.yaml file to optimize your OpenStack network for OVS-DPDK. See https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/network_functions_virtualization_planning_and_configuration_guide/part-dpdk-configure#proc_derive-dpdk for details.
Add the custom resources for OVS-DPDK under
resource_registry:resource_registry: # Specify the relative/absolute path to the config files you want to use for override the default. OS::TripleO::ComputeOvsDpdk::Net::SoftwareConfig: nic-configs/computeovsdpdk.yaml OS::TripleO::Controller::Net::SoftwareConfig: nic-configs/controller.yamlresource_registry: # Specify the relative/absolute path to the config files you want to use for override the default. OS::TripleO::ComputeOvsDpdk::Net::SoftwareConfig: nic-configs/computeovsdpdk.yaml OS::TripleO::Controller::Net::SoftwareConfig: nic-configs/controller.yamlCopy to Clipboard Copied! Toggle word wrap Toggle overflow Under
parameter_defaults, set the tunnel type and the tenant type tovxlan:NeutronTunnelTypes: 'vxlan' NeutronNetworkType: 'vxlan'
NeutronTunnelTypes: 'vxlan' NeutronNetworkType: 'vxlan'Copy to Clipboard Copied! Toggle word wrap Toggle overflow Under
parameters_defaults, set the bridge mappings:# The OVS logical->physical bridge mappings to use. NeutronBridgeMappings: 'tenant:br-link0' OpenDaylightProviderMappings: 'tenant:br-link0'
# The OVS logical->physical bridge mappings to use. NeutronBridgeMappings: 'tenant:br-link0' OpenDaylightProviderMappings: 'tenant:br-link0'Copy to Clipboard Copied! Toggle word wrap Toggle overflow Under
parameter_defaults, set the role-specific parameters for theComputeOvsDpdkrole:Copy to Clipboard Copied! Toggle word wrap Toggle overflow NoteYou must assign at least one CPU (with sibling thread) on each NUMA node with or without DPDK NICs present for DPDK PMD to avoid failures in creating guest instances.
NoteThese huge pages are consumed by the virtual machines, and also by OVS-DPDK using the
OvsDpdkSocketMemoryparameter as shown in this procedure. The number of huge pages available for the virtual machines is thebootparameter minus theOvsDpdkSocketMemory.You must also add
hw:mem_page_size=1GBto the flavor you associate with the DPDK instance.NoteOvsDPDKCoreListandOvsDpdkMemoryChannelsare the required settings for this procedure. Attempting to deploy DPDK without appropriate values causes the deployment to fail or lead to unstable deployments.
3.5.4.3. Configuring the Controller node
Create the control plane Linux bond for an isolated network.
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Assign VLANs to this Linux bond.
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Create the OVS bridge for access to the floating IPs into cloud networks.
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
3.5.4.4. Configuring the Compute node for DPDK interfaces
Create the compute-ovs-dpdk.yaml file from the default compute.yaml file and make the following changes:
Create the control plane Linux bond for an isolated network.
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Assign VLANs to this Linux bond.
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Set a bridge with a DPDK port to link to the controller.
Copy to Clipboard Copied! Toggle word wrap Toggle overflow NoteTo include multiple DPDK devices, repeat the
typecode section for each DPDK device you want to add.NoteWhen using OVS-DPDK, all bridges on the same Compute node should be of type
ovs_user_bridge. The director may accept the configuration, but Red Hat OpenStack Platform does not support mixingovs_bridgeandovs_user_bridgeon the same node.
3.5.4.5. Deploying the overcloud
Run the overcloud_deploy.sh script to deploy the overcloud.
3.6. Install OpenDaylight with L2GW support
This feature is available in this release as a Technology Preview, and therefore is not fully supported by Red Hat. It should only be used for testing, and should not be deployed in a production environment. For more information about Technology Preview features, see Scope of Coverage Details.
Layer 2 gateway services allow a tenant’s virtual network to be bridged to a physical network. This integration enables users to access resources on a physical server through a layer 2 network connection rather than through a routed layer 3 connection. This means extending the layer 2 broadcast domain instead of going through L3 or Floating IPs.
3.6.1. Prepare L2GW deployment files
To deploy OpenDaylight with L2GW support, use the neutron-l2gw-opendaylight.yaml file in the /usr/share/openstack-tripleo-heat-templates/environments directory. If you need to change the settings in that file, do not modify the existing file. Instead, create a new copy of the environment file that contains the necessary parameters.
If you want to deploy OpenDaylight and L2GW with the default settings, you can use neutron-l2gw-opendaylight.yaml in the /usr/share/openstack-tripleo-heat-templates/environments/services-docker directory.
The default file contains these values:
3.6.2. Configuring OpenDaylight L2GW deployment
You can configure the service by changing the values in the neutron-l2gw-opendaylight.yaml file:
|
|
Comma-separated list of service plugin entrypoints to be loaded from the |
|
|
Defines the provider that should be used to provide this service. Defaults to |
|
| Sets the name of the default interface. |
|
| Sets the name of the default device. |
|
|
Specifies the service quota for the L2 gateway. Defaults to |
|
| Specifies the monitoring interval for the L2GW service. |
3.6.3. Install OpenDaylight with L2GW
Before you start
- Install the undercloud. For more information, see Installing the undercloud.
- Create environment files with links to overcloud container images. For more information, see Preparing the installation of overcloud with OpenDaylight.
- Prepare the role file to configure OpenDaylight in a custom role with the SR-IOV support. For more information, see Prepare the L2GW deployment files.
Procedure
- Run the deployment command with the necessary environment files to enable the L2GW functionality with OpenDaylight.
Environment files present in the deployment command overwrite environment files that you include earlier in the command. You must pay attention to the order of the environment files that you include to avoid overwriting parameters accidentally.
You can override some of the parameters by creating a minimal environment file that sets only the parameters that you want to change and combining it with the default environment files.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}