Installing Contrail Cluster using the Contrail Command UI

Requirements

• Contrail Controller — 8 vCPU, 64GB memory, 300GB storage.

• OpenStack Controller — 4 vCPU , 32GB memory, 100GB storage.

• Contrail Server Node (CSN) — 4 vCPU, 16GB memory, 100GB storage.

• Compute nodes— Dependent on the workloads.

For a list of supported platforms, see Supported Platforms Contrail 5.1.

Overview

Contrail Cluster is an OpenStack orchestration coupled with the Contrail Networking plugin.

Topology

Consider a sample cluster topology, with a non-HA environment of one Contrail Controller and one OpenStack Controller, one compute node and one CSN, as displayed in Figure 1.

Figure 1: Sample Contrail Cluster Topology

Configuration

Deploying a Contrail Cluster

Step-by-Step Procedure

1. Login to Contrail Command UI.

   The default username is root and the default password is contrail123.

2. The default username for server is root and the default password is c0ntrail123.

   You can create new server credentials

   

3. Add physical servers. You can add a server in the following two ways:

   • One by one

   • CSV file bulk import

   • One by one: You can add each server one by one using the default credentials or any desired credentials from the drop down list. To add servers one by one, you must enter the following mandatory parameters:

     • Hostname

     • Management IP address

     • Management Interface

   • CSV file bulk import: You can upload a CSV file which contains the details of each server. This CSV file must conform to the Contrail Command format.

     You can download the CSV template from Contrail Command and reuse the template as per your requirements.

     To download a sample CSV file, navigate to Infrastructure > Servers > Add Servers in the Contrail Command UI.

     Use the Bulk Import option for large deployments. Bulk Import option requires a CSV file input.

     Click Bulk Import (csv), to download the template.

     A sample CSV file is shown here:

     content_copy zoom_out_map

     Workload Type,HostName,Management IP,Disk Partition,Network Interface,MAC address,IPMI Driver,IPMI Address,IPMI UserName,IPMI Password,Memory mb,CPU's,CPU Arch,Local gb,Capabilities,Number of Network Interfaces,Interface Name,Interface MAC Address,Interface IP,Enable PXE,Interface Name,Interface MAC Address,Interface IP,Enable PXE
     
     physical,5c10s9,10.87.74.69,,enp4s0f0,,,,,,,,,,,2,enp4s0f0,,10.87.74.69,,ens2f0,,10.1.0.2,
     
     physical,5c10s7-node1,10.87.74.65,,eno1,,,,,,,,,,,2,eno1,,10.87.74.65,,ens2f1,,10.1.0.3,
     
     physical,5c10s7-node3,10.87.74.67,,eno1,,,,,,,,,,,2,eno1,,10.87.74.67,,ens2f1,,10.1.0.67,
     
     physical,5c10s12,10.87.74.71,,eno1,,,,,,,,,,,2,eno1,,10.87.74.71,,ens1f0,,10.1.0.66,

     Note

     The demo topology above has only one compute node. If you are deploying additional compute nodes, you must include them in the CSV file.

   Figure 2: Add Server

   

4. Create a cluster.

   Click Provisioning Manager > Create Cluster

   If Container registry = hub.juniper.net/contrail . This registry is secure. Unselect the Insecure box.

   Also, Contrail version = contrail_container_tag for your release of Contrail as listed in README Access for Contrail .

   Default vRouter Gateway = Default gateway for the compute nodes. If any one of the compute nodes has a different default gateway than the one provided here, enter that gateway in step 7 and step 8 for service nodes.

   Set the order of Encapsulation Priority for the EVPN supported methods - MPLS over UDP, MPLS over GRE And VxLAN.

   content_copy zoom_out_map

   VXLAN, MPLSoUDP, MPLSoGRE

   Select Show Advanced Options. Add the following configuration parameters:

   • CONTROLLER_NODES = List of comma separated mgmt interface IP addresses of the Contrail controller

   • CONTROL_NODES = List of comma seperated data interface IP addresses of the Contrail controller

   • TSN_NODES = List of comma seperated data interface IP addresses of the Contrail service nodes

   • CONTRAIL_CONTAINER_TAG = container_tag-ocata or container_tag-queens

   Figure 3: Create Cluster

   

5. Select the contrail-control node.

   Figure 4: Select Control Nodes

   

   Enable High availability mode if you have HA setup for controller node. Select all the control nodes from Available servers list.

6. Select the orchestration type and nodes.

   The supported orchestrators are OpenStack and Kubernetes.

   Select Show Advanced option to customize your deployment and then select Orchestration Nodes.

   In order to run OpenStack services on the control data network, set the following parameters:

   • Control & Data Network Virtual IP address: It is an internal VIP. e.g. - 10.87.74.100

   • Management Network Virtual IP address: It is an external VIP. e.g. - 10.1.0.100

   • keepalived_virtual_router_id: (Optional). It can be set to any value between 0-255. The default value is 51.

   Add the following under custom configuration for VM based setup:

   content_copy zoom_out_map

   nova.conf: |
                [libvirt]
                virt_type=qemu
                cpu_mode=none
   

   Note

   Minimum 8 indent spaces are required for lines following the nova.conf.

   In Contrail Command, key-value pairs handle parameters that be enabled or disabled in Kolla Global.

   Set the following in Kolla Globals:

   content_copy zoom_out_map

   enable_ironic = no
   enable_swift = yes
   swift_disk_partition_size = 10GB
   

   Note

   The default value of swift_disk_partition_size is 5 GB. If you have 2 or more images, you must have at least 10 GB allocated to swift_disk_partition_size for hitless image upload procedure.

   If Ironic is not needed and if you are not going to use Life Cycle Management in Contrail Command then you need not deploy Ironic.

   Swift can be enabled for Image management uses case, this parameter is disabled by default.

   Compute node kernel version = kernel-3.10.0-862.3.2.el7.x86_64; Else kernel upgrade is required.

   To configure kolla password add keystone_admin_password<password> key-value pair in the kolla passwords section. This password will be used for logging onto the contrail command UI after the provisioning completes.

   Figure 5: Select Orchestrator Nodes

   

   Select the Openstack (orchestration) node.

   
7. Select the Compute Nodes. For each compute node, enter the gateway, if it is different from what was added in the global parameters in step 4. Then set the mode.

   As of now, only Kernel mode is supported

   Figure 6: Select Compute Nodes

   

8. Select the Contrail Service Node.

   Figure 7: Select Contrail Service Nodes

   

9. (Optional) You can add a new server to install AppFormix.

   For details, refer to Installing AppFormix using Contrail Command.

   
10. Verify the summary of your cluster configuration and click Provision.

    Figure 8: Verify Summary