New and Changed Features

Inter Subcluster Route Filtering

Contrail Networking Release 2005 supports inter subcluster route filtering (Beta). With this release, a new extended community called origin-sub-cluster (similar to origin-vn) is added to all routes originating from a subcluster.

The format of this new extended community is subcluster:<asn>:<id>.

This new extended community is added by encoding the subcluster ID in the ID field within the extended community. The subcluster ID helps you determine the subcluster from which the route originated, and is unique for each subcluster.

For more information, see Remote Compute.

Kubernetes 1.14.8 Support

Contrail CNI is qualified with Kubernetes version 1.14.8 in Contrail Networking Release 2005.

Zero Impact Upgrade: Upgrading Contrail Networking Software without Rebooting Compute Nodes with Kernel-mode vRouters

Starting in Contrail Networking Release 2005, Contrail Networking supports huge pages in environments where compute nodes are using kernel-mode vRouters and the environment is deployed using Red Hat Openstack or Juju. Huge page support for kernel-mode vRouters allows the Zero Impact Upgrade (ZIU) procedure to complete Contrail Networking software upgrades without rebooting compute nodes. For additional information, see Updating Contrail Networking using the Zero Impact Upgrade Process in an Environment using Red Hat Openstack, Updating Contrail Networking using the Zero Impact Upgrade Procedure in a Canonical Openstack Deployment with Juju Charms, and Installing Contrail with OpenStack by Using Juju Charms.

Zero Impact Upgrade: Contrail Networking Software Upgrades in Environments Deployed using Ansible

Starting in Contrail Networking Release 2005, you can use the Zero Impact Upgrade (ZIU) procedure to upgrade Contrail Networking software in environments that are deployed using Ansible. For additional information, see How to Perform a Zero Impact Contrail Networking Upgrade using Ansible.

Deploying Contrail Command and Importing a Contrail Cluster Using Juju in a Canonical Openstack Environment

Starting in Contrail Networking Release 2005, you can deploy Contrail Command and import an existing Contrail Cluster into Contrail Command with a single procedure using Juju in environments where Canonical Openstack is the orchestration platform. For additional information, see How to Deploy Contrail Command and Import a Cluster Using Juju in a Canonical Openstack Environment.

Installation Enhancements for Contrail Command Installations with Contrail Insights and Contrail Insights Flows

Starting in Contrail Networking Release 2005, you can enable Contrail Insights and Contrail Insights Flows without adding the /opt/software/appformix:/opt/software/appformix and /opt/software/xflow:/opt/software/xflow user command volume paths in the command_servers.yml file. This update to the command_servers.yml file was required before enabling Contrail Command in environments using Contrail Insights and Contrail Insights Flows. Contrail Insights and Contrail Insights Flows used to be named AppFormix and AppFormix Flows respectively. For additional information, see Installing Contrail Command.

Adding or Deleting Flow Collector Nodes in Contrail

Support to add a flow-collector node or delete an existing flow-collector node by modifying the instances.yml file. For more information, see

For more information, see Adding or Deleting Flow Collector Nodes in Contrail.

Configuring DCI-Gateway Role on MX Series Routers

Starting in Contrail Networking Release 2005, you can configure the DCI-Gateway routing-bridging role on MX240, MX480, MX960, and MX10003 devices. These MX series devices can then be used in spine deployments.

For more information, see Supported Hardware Platforms and Associated Node Profiles and Roles and Data Center Interconnect.

Enhanced Routing Policies to Support QFX Series Devices in Contrail Networking

Contrail Networking Release 2005 enables you to create routing policies for QFX series devices. In earlier Contrail Networking releases you could create routing policies for vRouters only. From the Contrail Command UI you can create a routing policy for a physical device (QFX Series devices) or a vRouter. Navigate to Overlay>Routing Policies>Add>Create Routing Policy to create a routing policy with routing policy terms supported by QFX Series devices. Select Physical Device from the Type field to create a routing policy for QFX Series devices.

Contrail Networking Release 2005 enables you to create routing policies for QFX series devices in the Contrail Command user interface (UI). In releases prior to release 2005, you could create routing policies on vRouters only. To create a routing policy on a QFX series device, navigate to Overlay>Routing>Routing Policies>Add and select Physical Device in the Type field.

For more information, see Creating Routing Policies for Junos Physical Devices in Contrail Networking.

Configuring BFD with eBGP, Static Route, OSPF, and PIM Routing Protocols

Starting in Contrail Networking Release 2005, you can configure BFD with eBGP, Static Route, OSPF, and PIM routing protocols. For more information, see Connecting to Third-Party PNF Devices.

Support for Configuring PIM and OSPF Routing Protocols

You can use the Contrail Command user interface (UI) to connect the border gateway devices to third-party devices that are not managed by Contrail Networking. With Contrail Networking Release 2005, you can also configure Protocol Independent Multicast (PIM) and Open Shortest Path First (OSPF) routing protocols between a logical router and an unmanaged third-party device. As a result, configuration is pushed to the border gateway devices and a connection is formed between the fabric and the external network through the third-party unmanaged device.

For more information, see Connecting to Third-Party PNF Devices.

Support for Logical Router Interconnect in Contrail Networking

Contrail Networking Release 2005 supports the logical router interconnect (LR Interconnect) feature that enables you to leak routes from a source logical router to multiple destination logical routers that are deployed in the same fabric. The source logical router leaks routes using an export source. In the Contrail Command user interface (UI), navigate to Overlay>Interconnects>LR Interconnects>Create and select Routing Policy or Virtual Networks as the Export Source, which the source logical router uses to leak routes to all the destination logical routers.

For more information, see Logical Router Interconnect.

Support for Octavia as LBaaS

Starting in Contrail Networking Release 2005, Contrail Networking supports Octavia as LBaaS. The Neutron LBaaS plugin is no longer available in OpenStack Train release. If you want to use legacy Contrail load balancer, you can use VNC or Contrail Command. For details, refer to Installing OpenStack Octavia LBaaS with Contrail Networking and Installing OpenStack Octavia LBaaS in Canonical Deployment.

What’s New Panel in Contrail Command

Starting with Contrail Networking Release 2005, you can use the What’s New panel within Contrail Command to gather a summary list of the new Contrail Networking features in your Contrail Networking release. The What’s New panel provides a high-level description of each new feature and a See Release Notes option that takes you to the Contrail Networking Release Notes for additional feature information. You can access the What’s New panel by selecting the What’s New option in the ? help menu.