Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Setting Up the Infrastructure (Contrail Networking Release 21.4.L4 or Later)

Follow this topic to set up the infrastructure for Contrail Networking deployment in a RHOSP 17.1 environment when you are using Contrail Networking Release 21.4.L4 or later.

When to Use This Procedure

Before you can deploy your undercloud and overcloud, set up your node and network infrastructure.

Figure 1 shows an example deployment consisting of three OpenStack Controller nodes, three Contrail Controller nodes, a single Compute node, and the Director where we run our undercloud, as follows:

  • All nodes connect to the management (green) network. We use this network to SSH into the nodes and to allow the nodes to reach outside networks. The subnet for the management network is 10.102.70.0/24 and the gateway is 10.102.70.1 (not shown).This is an untagged network.

  • All nodes connect to the control plane (blue) network. This network contains all the overcloud control plane networks, including the provisioning network that the director uses to run IPMI and provision the overcloud. The provisioning network is untagged but all the other control plane networks are tagged. The subnet for the provisioning network is 192.168.213.0/24.

  • The Contrail Controller and Compute nodes connect to the tenant (orange) network. This is the data network that carries tenant traffic. This is an untagged network. The subnet for the tenant network is 192.168.33.0/24.

  • The director has an IP address of 192.168.213.10/24 on the provisioning network and 10.102.70.10/24 on the management network.

We will use this deployment example to show you how to install Contrail.

Figure 1: Contrail Deployment Example Contrail Deployment Example

Figure 2 shows the VLAN and IP subnet configuration for the control plane in our example.

  • The OpenStack Controller nodes connect to the management, provisioning, internal api, external, storage, and storage management networks.

  • The Contrail Controller nodes connect to the management, provisioning, internal api, external, and tenant networks.

  • The Compute node connects to the management, provisioning, internal api, storage, and tenant networks.

  • The Director (not shown) connects to the management and provisioning networks.

Figure 2: Control Plane VLANs Control Plane VLANs

Set Up the Infrastructure

  1. Set up the eight bare metal servers with interfaces as shown in Figure 1.
  2. Set up the management, control plane, and tenant networks (including VLANs) as shown in Figure 1 and Figure 2, including the 10.102.70.1/24 gateway on the management network.
  3. Install a fresh RHEL 9.2 OS on the Director node.
  4. Configure the Director for baseline functionality.

    • SSH root access

    • NTP

    • DNS

    • Static IP addresses on the enp1s0 interface (10.102.70.10/24) and enp2s0 interface (192.168.213.10/24)

    • Gateway (10.102.70.1) as the default route on the management network