Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Architecture of the Contrail Cloud Implementation in the Centralized Deployment

 

This section describes one possible architecture of the components in the Contrail Cloud implementation used in the centralized deployment.

Architecture of the Contrail Cloud Implementation

The centralized deployment uses the Contrail Cloud implementation to support the service provider’s cloud in a network point of presence (POP). The Contrail Cloud implementation consists of the hardware platforms, including the servers, and Contrail OpenStack software. Figure 1 illustrates the Contrail Cloud implementation. The Contrail Service Orchestration (CSO) software is installed on one or more servers in the Contrail Cloud implementation to complete the deployment.

Figure 1: Architecture of Contrail Cloud Implementation
Architecture of Contrail Cloud
Implementation

In the Cloud CPE Centralized Deployment Model:

  • The MX Series router provides the gateway to the service provider’s cloud.

  • The EX Series switch provides Ethernet management and Intelligent Platform Management Interface (IPMI) access for all components of the Cloud CPE Centralized Deployment Model. Two interfaces on each server connect to this switch.

  • The QFX Series switch provides data access to all servers.

  • The number of servers depends on the scale of the deployment and the high availability configuration. You must use at least two servers and you can use up to five servers.

  • Each server supports four nodes. The function of the nodes depends on the high availability configuration and the type of POP.

Architecture of the Servers

The configuration of the nodes depends on whether the Contrail Cloud implementation is in a regional POP or central POP and on the high availability configuration. Each node is one of the following types:

  • Contrail Service Orchestration node, which hosts the Contrail Service Orchestration software.

  • Contrail controller node, which hosts the Contrail controller and Contrail Analytics.

  • Contrail compute node, which hosts the Contrail Openstack software and the virtualized network functions (VNFs).

The Contrail Cloud implementation in a central POP contains all three types of node. Figure 2 shows the configuration of the nodes in the Contrail Cloud implementation in the central POP for a deployment that offers neither Contrail nor Contrail Service Orchestration high availability:

  • Server 1 supports one Contrail controller node, two Contrail compute nodes, and one Contrail Service Orchestration node.

  • Server 2 and optional servers 3 through 5 each support four Contrail compute nodes.

Figure 2: Architecture of Servers in the Central POP for a Non-Redundant Installation
Architecture of Servers
in the Central POP for a Non-Redundant Installation

Figure 3 shows the configuration of the nodes in the Contrail Cloud implementation in the central POP for a deployment that offers both Contrail and Contrail Service Orchestration high availability:

  • Servers 1, 2, and 3 each support one Contrail controller node for Contrail redundancy.

  • Servers 1 and 2 each support one Contrail Service Orchestration node for Contrail Service Orchestration redundancy.

  • Other nodes on servers 1, 2, and 3 are Contrail compute nodes. Optional servers 4 through 7 also support Contrail compute nodes.

Figure 3: Architecture of Servers in the Central POP for a Redundant Installation
Architecture of Servers in the
Central POP for a Redundant Installation

The Contrail Cloud implementation in a regional POP contains only Contrail nodes and not Contrail Service Orchestration nodes. In a deployment that does not offer Contrail high availability, the regional Contrail Cloud implementations support:

  • One Contrail controller node and three Contrail compute nodes on server 1.

  • Four Contrail compute nodes on server 2 and on optional servers 3 through 5.

In a deployment that offers Contrail high availability, the regional Contrail Cloud implementations support:

  • One Contrail controller node for Contrail redundancy on servers 1, 2, and 3.

  • Three Contrail compute nodes on servers 1, 2, and 3.

  • Four Contrail compute nodes on optional servers 4 through 7.

Architecture of the Contrail Nodes

Each Contrail controller node uses Contrail vRouter over Ubuntu and kernel-based virtual machine (KVM) as a forwarding plane in the Linux kernel. Use of vRouter on the compute node separates the deployment’s forwarding plane from the control plane, which is the SDN Controller in Contrail OpenStack on the controller node. This separation leads to uninterrupted performance and enables scaling of the deployment. Figure 4 shows the logical representation of the Contrail controller nodes.

Figure 4: Logical Representation of Contrail Controller Nodes
Logical Representation
of Contrail Controller Nodes

A Contrail compute node hosts Contrail OpenStack, and the VNFs. Contrail OpenStack resides on the physical server and cannot be deployed in a VM. Each VNF resides in its own VM. Figure 5 shows the logical representation of the Contrail compute nodes.

Figure 5: Logical Representation of Contrail Compute Nodes
Logical Representation
of Contrail Compute Nodes