Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Architecture of the Cloud CPE Centralized Deployment Model

    This section describes the architecture of the components in the Cloud CPE Centralized Deployment Model.

    Architecture of the CCRA

    The Cloud CPE Centralized Deployment Model uses the Contrail Cloud Reference Architecture (CCRA) to support the service provider’s cloud in a network point of presence (POP). The CCRA consists of the hardware platforms, including the servers, and Contrail OpenStack software. Figure 1 illustrates the CCRA.

    Figure 1: Architecture of CCRA

    Architecture of CCRA

    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

    Each server supports four nodes. The configuration of the nodes depends on whether the CCRA 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
    • Contrail configure and control node
    • Contrail compute node

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

    • Server 1 supports one Contrail configure and control 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 a Non-Redundant Installation

    Architecture of Servers
in a Non-Redundant Installation

    Figure 3 shows the configuration of the nodes in the CCRA 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 configure and control 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 and 5 also support Contrail compute nodes.

    Figure 3: Architecture of Servers in a Redundant Installation

    Architecture of Servers in a
Redundant Installation

    The CCRA 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 CCRAs support:

    • One Contrail configure and control 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 CCRAs support:

    • One Contrail configure and control 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 and 5.

    Architecture of Nodes in Regional POPs and Central POP for a Scaled Installation with High Availability shows the distribution of the nodes in the CCRAs in regional POPs and the central POPs for a deployment that offers both Contrail and Contrail Service Orchestration high availability.

    Architecture of the Contrail Nodes

    Each Contrail configure and control 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 configure and control node. This separation leads to uninterrupted performance and enables scaling of the deployment. Figure 4 shows the architecture of the Contrail configure and control nodes.

    Figure 4: Architecture of Contrail Configure and Control Nodes

    Architecture
of Contrail Configure and Control 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 architecture of the Contrail compute nodes.

    Figure 5: Architecture of Contrail Compute Nodes

    Architecture
of Contrail Compute Nodes

    Architecture of the Contrail Service Orchestration Nodes

    The Contrail Service Orchestration nodes support the following components in multiple VMs:

    • Contrail Service Orchestration components
    • Junos Space Virtual Appliance and database
    • Third-party software applications

    In a Cloud CPE Centralized Deployment Model that is not configured for Contrail Service Orchestration redundancy, there is one Contrail Service Orchestration node on server 1 in the CCRA.

    In a Cloud CPE Centralized Deployment Model that is configured for Contrail Service Orchestration redundancy, there is one Contrail Service Orchestration node on both server 1 and server 2 in the CCRA.

    The architecture of the nodes depends on whether the Contrail Service Installation is redundant or non-redundant.

    See Details of VMs on the Contrail Service Orchestration Node for a Non-Redundant Configuration and Details of VMs on Contrail Service Orchestration Nodes for a Redundant Configuration for information about the VMs and the Contrail Service Orchestration components that reside in them.

    Modified: 2016-06-02