Chapter 3. Configuring OVN gateways for a Red Hat OpenStack Services on OpenShift deployment

Procedure

1. Open the OpenStackControlPlane CR definition file, openstack_control_plane.yaml.

2. Add the following ovnController configuration, including nicMappings, to the ovn service configuration:

   ovnController:
   
   spec:
     ...
   ovn:
     template:
       ovnController:
         networkAttachment: tenant
         nicMappings:
            <network_name: nic_name>

   Copy to Clipboard Toggle word wrap
   • Replace <network_name> with the name of the physical provider network your gateway is on. This should match the value of the --provider-physical-network argument to the openstack network create command used to create the network. For example, datacentre.
   • Replace <nic_name> with the name of the NIC connecting to the gateway network, such as enp6s0.
   • Optional: Add additional <network_name>:<nic_name> pairs under nicMappings as required.

3. Update the control plane:

   $ oc apply -f openstack_control_plane.yaml -n openstack

   Copy to Clipboard Toggle word wrap

   The ovn-operator creates the network attachment definitions, adds them to the pods, creates an external bridge, and configures external-ids:ovn-bridge-mappings. The setting external-ids:ovn-cms-options=enable-chassis-as-gw is configured by default.

4. Wait until RHOCP creates the resources related to the OpenStackControlPlane CR. Run the following command to check the status:

   $ oc get openstackcontrolplane -n openstack
   NAME 						STATUS 	MESSAGE
   openstack-control-plane 	Unknown 	Setup started

   Copy to Clipboard Toggle word wrap

   The OpenStackControlPlane resources are created when the status is "Setup complete".

   Tip

   Append the -w option to the end of the get command to track deployment progress.

5. Confirm that the control plane is deployed by reviewing the pods in the openstack namespace:

   $ oc get pods -n openstack

   Copy to Clipboard Toggle word wrap

   The control plane is deployed when all the pods are either completed or running. Verify that ovn-controller and ovn-controller-ovs pods are running, and that the number of running pods is equal to the number of OCP control plane nodes where OpenStack control plane services are running.

Verification

1. Run a remote shell command on the OpenStackClient pod to confirm that the OVN Controller Gateway Agents are running on the control plane nodes:

   $ oc rsh -n openstack openstackclient openstack network agent list

   Copy to Clipboard Toggle word wrap

   Example output

   +--------------------------------------+------------------------------+---------+
   | ID                                   | agent_type                   | host    |
   +--------------------------------------+----------------------------------------+
   | 5335c34d-9233-47bd-92f1-fc7503270783 | OVN Controller Gateway agent | ctrl0   |
   | ff66288c-5a7c-41fb-ba54-6c781f95a81e | OVN Controller Gateway agent | ctrl1   |
   | 5335c34d-9233-47bd-92f1-fc7503270783 | OVN Controller Gateway agent | ctrl2   |
   +--------------------------------------+----------------------------------------+

   Copy to Clipboard Toggle word wrap

Procedure

1. Open your OpenStackControlPlane custom resource (CR) file, openstack_control_plane.yaml, on your workstation.

2. If there is an ovnController section:

   1. Remove the ovnController section.

   2. Update the control plane:

      $ oc apply -f openstack_control_plane.yaml -n openstack

      Copy to Clipboard Toggle word wrap