Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

New and Changed Features From Previous Contrail Cloud Releases


This section contains the new or changed features for the specified Contrail Cloud Release.

New and Changed Features in Contrail Cloud Release 13.1

The features listed in this section are new as of Contrail Cloud Release 13.1. A brief description of each feature is included.

Product Components

  • Contrail Networking Release 1908

  • AppFormix Release 3.1.0

  • Red Hat OpenStack 13—OpenStack Queens Version (Red Hat CDN sync 5-August-2019)

  • RHEL7.6—Linux Kernel Version 3.10.0-957.27.2 (Red Hat CDN sync 5-August-2019)

  • Red Hat Ceph Storage 3.2 (Red Hat CDN sync 5-August-2019)

OpenStack Compute

  • Multiple compute and storage roles allowed for different physical resources.

    A profile is a homogenous group. A role can use multiple profiles as sub-roles to allow heterogeneous hardware to use the same overcloud role.

Ceph Storage

  • Ceph Storage 3.2 support with full support for BlueStore Ceph backend.

    For more information, see BlueStore: Improved performance with Red Hat Ceph Storage 3.2

  • Encrypted disk contents for Ceph OSD storage.

  • Ceph journal device configuration for legacy filestore.

  • RGW for Object Store (Swift/S3) backend.

  • Allow pools to be disabled.

    Ceph pools for OpenStack services that are not used can be disabled. As an example in Contrail Cloud, Gnocchi and Ceilometer services are disabled by default.

  • External Ceph cluster support.

    Contrail Cloud allows for integration of pre-existing Ceph clusters as opposed to creating a new Ceph cluster for deployment.

OpenStack Networking

  • IPv6 supported in the overcloud networks.

    The supported networks are:

    • External

    • Storage

    • StorageMgmt

    • Management

    Networks that do not support IPv6 in the overcloud:

    • ControlPlane

    • InternalAPI

    • Tenant

    For more information, see IPV6 NETWORKING FOR THE OVERCLOUD.

  • Multiple subnet support for compute and storage.

    This aligns with Red Hat terminology for a Spine/Leaf Architecture. For more information, see SPINE LEAF NETWORKING.

  • Changed the default subnet used for the provisioning and controlplane activities from 192.0.2* to 192.168.213*.

    • Changed subnet default decreases the probability of an IP address already being used.

    • The default can be overridden by the user if necessary.

  • Sample configs use Linux bond for OVS bridging in the underlay (as opposed to OVS bond in previous Contrail Cloud releases).

Contrail Networking

  • TLS encryption certificate management for Sandesh and XMPP Contrail protocols.

  • SR-IOV (coexists with either kernel or DPDK vRouter) support using the new role ComputeSriov.

  • TSN support.

    A new ContrailTsn role was added. TSN is a container running in a separate VM added to the Control Host.

  • Custom container settings.

    Custom container settings allows passthrough values to set environment properties for Contrail containers

    For more information, see the sample files in the samples/features/extra-config/ directory.

  • Contrail Command UI Integration.

    Only the UI portion of Contrail Command is added in this release. Other capabilities of Contrail Command will be considered in future releases.

  • SDN gateway config with FIPs.

    Using the site.yml file, the user can provision SDN gateway configurations.

    For more information, see the sample files in the samples/features/provision-sdn-gateway/ directory.


  • Sensitive information at-rest encryption.

    • Supports Ansible Vault for secure storage of sensitive information. All passwords, keys, and other sensitive information are move to an encrypted vault config file.

    • Root password can be changed.

    • SSH keys can have a passphrase.

    • Certificate CA can be imported.

  • Automated deployment of compute and storage in small batches.

    In the event of large deployments, updating the entire set of compute and storage nodes can take a very long time. This can potentially lead to timeout errors and a failed deployment. The user can now configure how many nodes are to be deployed/updated in a single batch. The process will cycle through all the batches until the complete set of compute and storage nodes have been deployed.

  • Support for custom post-deploy actions.

    Typical actions include system tuning (CPU performance mode, file system tuning), blacking listing module, and more.

    These actions can be defined in the site.yml file. Examples are provided in the samples/features/extra-action/ directory

  • UEFI boot support.

    Contrail Cloud 13.1 added support for UEFI. Previous versions only supported legacy PXEboot

  • LLDP support on the jump host, control host, and all overcloud roles.

    This allows the user to discover server networking info from the switch or from the server. This information makes troubleshooting initial fabric connectivity easier.

  • Root disk specification.

    This can be configured in the site.yml file. For more information, see Appendix A of the Contrail Cloud Deployment Guide.

  • Node configuration validation tools.

    This is a configuration tool to check that physical resources correctly match roles intended for the nodes. The validation tool allows the user to query properties of nodes and compare the differences between nodes.

    For more information, see the Contrail Cloud Deployment Guide.

  • TripleO templates are validated before deployment start.

    An error in a TripleO file can take significant time to be found during deployment. This tool checks generated Heat templates for the most common errors before deployment starts. This is intended to save a significant amount of time should error detection occur.

OpenStack Deployment Enhancements

  • Admin password can be configured.

  • OpenStack CLI bash autocomplete on the undercloud.

  • Post deployment validation with Tempest.

    For more information, see the Contrail Cloud Deployment Guide.

  • Undercloud/Overcloud RabbitMQ tuning.

    Contrail Cloud applies best practice values to optimize RabbitMQ configuration. RabbitMQ tuning parameters are exposed in the site.yml file.

  • LDAP integration for Keystone

    LDAP integration for keystone example configuration can be seen in the site.yml file in the samples/features/ldap-backend-for-keystone-domains/ directory.


  • AppFormix.

    For more information, see AppFormix Documentation.

    • AppFormix is now set as an overcloud role.

    • Enable network topology view.

    • Allow virtual IP for the InternalAPI network.

    • Automation the addition of Contrail Config and Analytics REST API endpoints.

    • AppFormix plugin for HEAT overcloud service.

    • Custom plugin support.

New and Changed Features in Contrail Cloud Release 13.0.2

The features listed in this section are new as of Contrail Cloud Release 13.0.2.

  • Contrail Networking 5.0.2 is now distributed with Contrail Cloud 13.0.2. Contrail Networking 5.0.2 provides many fixes for issues (especially around DPDK). See the Contrail Networking Release Notes.

  • Contrail Cloud is delivered through the Contrail Cloud Repository Satellite. The Contrail Cloud Installer script, activation key, satellite DNS name, and satellite organization information is provided through a request to

New and Changed Features in Contrail Cloud Release 13.0

The features listed in this section are new as of Contrail Cloud Release 13.0.

  • Support for Red Hat OpenShift Platform 13 based on OpenStack Queens with container-based deployment.

  • Support for containerized Contrail Networking Release 5.0.1.

  • Support for AppFormix Release 2.16.6.

  • Support for Red Hat Enterprise Linux 7.5.

  • Single master script “” can be used to launch the 8 playbooks needed for Contrail Cloud deployment.

  • Networking layout is simplified and unified by using the os-net-config syntax and utility.

  • Disk layout on control-hosts is simplified and fully configuration driven.

  • Configuration has a tree structure which provides better logical organization and allows fine-grained overrides of default values.

  • Virtual machine(VM) networking layout is now configured in control-host-nodes.yaml.

  • Virtual machine (VM) data traffic was moved from the “InternalAPI” network to the “Tenant” network by default.

  • Service user is changed to “contrail” on control-hosts, appformix-nodes, and jumphost.

  • MAC addresses are no longer needed in inventory file.

  • Support for predictable node placement for control plane VMs.

  • Controller fencing support is automatically enabled on HA environments without user intervention.

  • Single root input/output virtualization (SR-IOV) supported as a Beta feature.