Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Miscellaneous

 

This section of the guide covers options available in Contrail Cloud.

Capsule Server Configuration

Capsule servers mirror content from a Satellite Server to establish content sources in various geographical locations. This enables host systems to pull content and configuration from the capsule servers in their location and not from the central Satellite Server. For additional information on capsule servers, see What Satellite Server and Capsule Server do from the Red Hat Satellite Installation Guide.

Figure 1 illustrates a capsule server topology.

Figure 1: Capsule Server Topology
Capsule Server Topology

The Capsule VMs in this topology must have access to the Internet. Internet access is required to connect with Juniper Satellite servers for Contrail Cloud and to connect with RedHat subscription managers servers. For a detailed capsule server installation procedure, see Installing Capsule Server from the Red Hat Satellite Installation Guide.

The procedure for installing capsule server in Contrail Cloud:

  1. Create a capsule VM using Red Hat Enterprise Linux 7.6.
  2. Install the capsule keys for Red Hat Enterprise Linux from the Contrail Cloud Satellite device. The capsule keys are used to encrypt communication between the Contrail Cloud satellite and the capsule. The keys also allow Red Hat Enterprise Linux to register the operating system and are required to enable Red Hat Subscription Manager.
  3. Register the Contrail Cloud satellite device with the Red Hat Openstack subscription manager:
  4. From the Red Hat Subscription Manager, get the ID of the pool with RedHat Satellite and capsule server.
  5. In Red Hat Subscription Manager, enable repositories.
  6. In Red Hat Subscription Manager, refresh the subscription manager.
  7. In Red Hat Subscription Manager, install the capsule server.
  8. Register your Capsule Server to the Contrail Cloud Satellite Server:
    • Create the certificates archive on the Contrail Cloud Satellite Server. This task requires access to the Contrail Cloud server and often has to be performed by a site’s Contrail Cloud administrator.

      The certificates are delivered as a tar file.

      A configuration snippet of the command that is executed by the Capsule Server administrator.

      Note

      The provided FQDN must be resolvable from the satellite server to the VM IP address with capsule server.

    • Run the capsule installation script with the provided certificates:

Deployment Validation Tools

The Contrail Cloud 13.1 software bundle includes scripts that assist with detecting connectivity and configuration issues.

This section provides information on these scripts.

Check Server Hardware Specifications Script

The inventory-assigne.sh script—which is stored in the /var/lib/contrail_cloud/introspection/ directory on the jumphost—can be used to generate a JSON file with full hardware specifications for each server in your Contrail Cloud environment. The script uses the Red Hat Ironic service to help generate the JSON file.

The node-configuration.py python script—which is stored in the /var/lib/contrail_cloud/scripts/ directory on the jumphost—can be used to simplify the process of gathering server hardware specification information from the generated JSON files.

Check Disk allocation, CPU architecture and memory

In the following example, the node-configuration.py script is run after the inventory-assigne.sh script to gather information about check disk allocations, CPU architecture, and memory information:

Check NUMA and numbers of NICs

In this example, you check the NUMA and NIC numbers after the inventory-assigne.sh script has been.

Additional information related to NICs and NUMAs can be gathered by running the node-configuration.py script from the jumphost:

Pre-Deployment Check

The Contrail Cloud software bundle includes a script to check a server deployment before installing the Red Hat OpenStack platform. We suggest running the script before deploying the OpenStack cluster. The process is outlined in the Contrail Cloud Deployment Guide.

The validation-node.sh script—which is stored in the /var/lib/contrail_cloud/scripts directory on the jumphost—should be run before the openstack-deploy.sh script. The validation-node.sh script validates the configuration YAML files for the following components:

  • Network for Openstack Controllers, Contrail Controller, Contrail Analytics and Analytics DB.

  • Networking for controller hosts and compute hosts.

  • Disk validation (comparing actual available disks with configured disks).

The following configuration snippet displays the process when the validation-node.sh script is run.

Note

The script verifies configuration parameters but cannot guarantee the success of the deployment.

Post-Deployment Check

The Contrail Cloud software bundle includes a set of Tempest test packages to check the health of the Contrail Cloud environment.

The Tempest test packages are launched using the overcloud-validation.sh script. The script runs the following Tempest test packages:

  • openstack-tempest

  • python2-cinder-tests-tempest

  • python2-horizon-tests-tempest

  • python2-keystone-tests-tempest

  • python2-neutron-tests-tempest

  • Contrail tempest checks including following scenarios: contrail, lbaasv2, pagination, sorting, security-group, ipam, port-security, binding, provider, agent, quotas, route-table, standard-attr-description, external-net, policy, router, allowed-address-pairs, extra_dhcp_opt, project-id, extra_lbaas_opts

Fabric Design

This reference architecture does not cover fabric design.

To configure an EVPN-VXLAN fabric that can be used by the nodes in a Contrail Cloud to transport Layer 2 and Layer 3 traffic, see Data Center Fabric Architecture Guide.