Chapter 2. Working with ML2/OVN

Procedure

1. Log in to your undercloud as the stack user.

2. In the template file, /home/stack/templates/containers-prepare-parameter.yaml, use ovs instead of ovn as value of the neutron_driver parameter:

   parameter_defaults:
     ContainerImagePrepare:
     - set:
         ...
         neutron_driver: ovs

3. In the environment file, /usr/share/openstack-tripleo-heat-templates/environments/services/neutron-ovs.yaml, ensure that the NeutronNetworkType parameter includes vxlan or gre instead of geneve.

   Example

   parameter_defaults:
     ...
     NeutronNetworkType: 'vxlan'

4. Run the openstack overcloud deploy command and include the core heat templates, environment files, and the files that you modified.

   Important

   The order of the environment files is important because the parameters and resources defined in subsequent environment files take precedence.

   $ openstack overcloud deploy --templates \
   -e <your_environment_files> \
   -e /usr/share/openstack-tripleo-heat-templates/environments/services/ \
   neutron-ovs.yaml \
   -e /home/stack/templates/containers-prepare-parameter.yaml \

Procedure

1. Log in to the undercloud host as the stack user and source the stackrc file.

   $ source stackrc

2. Choose the custom roles file that is appropriate for your deployment. Use it directly in the deploy command if it suits your needs as-is. Or you can generate your own custom roles file that combines other custom roles files.

   Deployment	Role	Role File
   Networker role	Networker	Networker.yaml
   Networker role with SR-IOV	NetworkerSriov	NetworkerSriov.yaml
   Co-located control and networker with SR-IOV	ControllerSriov	ControllerSriov.yaml

3. [Optional] Generate a new custom roles data file that combines one of these custom roles files with other custom roles files. Follow the instructions in Creating a roles_data file in the Advanced Overcloud Customization guide. Include the appropriate source role files depending on your deployment.
4. [Optional] To identify specific nodes for the role, you can create a specific hardware flavor and assign the flavor to specific nodes. Then use an environment file define the flavor for the role, and to specify a node count. For more information, see the example in Creating a new role in the Advanced Overcloud Customization guide.

5. Create an environment file as appropriate for your deployment.

   Deployment	Sample Environment File
   Networker role	neutron-ovn-dvr-ha.yaml
   Networker role with SR-IOV	ovn-sriov.yaml

6. Include the following settings as appropriate for your deployment.

   Deployment	Settings
   Networker role	ControllerParameters: OVNCMSOptions: "" ControllerSriovParameters: OVNCMSOptions: "" NetworkerParameters: OVNCMSOptions: "enable-chassis-as-gw" NetworkerSriovParameters: OVNCMSOptions: ""
   Networker role with SR-IOV	OS::TripleO::Services::NeutronDhcpAgent: OS::Heat::None ControllerParameters: OVNCMSOptions: "" ControllerSriovParameters: OVNCMSOptions: "" NetworkerParameters: OVNCMSOptions: "" NetworkerSriovParameters: OVNCMSOptions: "enable-chassis-as-gw"
   Co-located control and networker with SR-IOV	OS::TripleO::Services::NeutronDhcpAgent: OS::Heat::None ControllerParameters: OVNCMSOptions: "" ControllerSriovParameters: OVNCMSOptions: "enable-chassis-as-gw" NetworkerParameters: OVNCMSOptions: "" NetworkerSriovParameters: OVNCMSOptions: ""

7. Deploy the overcloud. Include the environment file in your deployment command with the -e option. Include the custom roles data file in your deployment command with the -r option. For example: -r Networker.yaml or -r mycustomrolesfile.yaml.

Verification steps - OVN deployments

1. Log in to a Controller or Networker node as the overcloud SSH user, which is heat-admin by default.

   Example

   ssh heat-admin@controller-0

2. Ensure that ovn_metadata_agent is running on Controller and Networker nodes.

   $ sudo podman ps | grep ovn_metadata

   Sample output

   a65125d9588d  undercloud-0.ctlplane.localdomain:8787/rh-osbs/rhosp16-openstack-neutron-metadata-agent-ovn:16.1_20200813.1  kolla_start           23 hours ago  Up 21 hours ago         ovn_metadata_agent

3. Ensure that Controller nodes with OVN services or dedicated Networker nodes have been configured as gateways for OVS.

   $ sudo ovs-vsctl get Open_Vswitch . external_ids:ovn-cms-options

   Sample output

   ...
       enable-chassis-as-gw
   ...

Verification steps - SR-IOV deployments

1. Log in to a Compute node as the overcloud SSH user, which is heat-admin by default.

   Example

   ssh heat-admin@compute-0

2. Ensure that neutron_sriov_agent is running on the Compute nodes.

   $ sudo podman ps | grep neutron_sriov_agent

   Sample output

   f54cbbf4523a  undercloud-0.ctlplane.localdomain:8787/rh-osbs/rhosp16-openstack-neutron-sriov-agent:16.2_20200813.1
   kolla_start  23 hours ago  Up 21 hours ago         neutron_sriov_agent

3. Ensure that network-available SR-IOV NICs have been successfully detected.

   $ sudo podman exec -uroot galera-bundle-podman-0 mysql nova -e 'select hypervisor_hostname,pci_stats from compute_nodes;'

   Sample output

   computesriov-1.localdomain	{... {"dev_type": "type-PF", "physical_network": "datacentre", "trusted": "true"}, "count": 1}, ... {"dev_type": "type-VF", "physical_network": "datacentre", "trusted": "true", "parent_ifname": "enp7s0f3"}, "count": 5}, ...}
   computesriov-0.localdomain	{... {"dev_type": "type-PF", "physical_network": "datacentre", "trusted": "true"}, "count": 1}, ... {"dev_type": "type-VF", "physical_network": "datacentre", "trusted": "true", "parent_ifname": "enp7s0f3"}, "count": 5}, ...}