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

    The Cloud CPE Centralized Deployment Model uses the Contrail Cloud Reference Architecture (CCRA) to support the service provider’s cloud. The CCRA consists of the hardware platforms, including the servers, and Contrail OpenStack software. The Contrail Service Orchestration software is installed on a server in the CCRA to complete the deployment model (Figure 1).

    Figure 1: Topology of Cloud CPE Centralized Deployment Model with CCRA and Contrail Service Orchestration

    Topology of Cloud CPE Centralized
Deployment Model with CCRA and Contrail Service Orchestration

    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.
    • One server supports the following nodes:
      • Contrail Service Orchestration node
      • Contrail configure and control node
      • Two Contrail compute nodes
    • Up to four additional servers, each with four nodes, act as additional Contrail compute nodes.
    • The Cloud CPE Centralized Deployment Model installer and its associated configuration file reside together in a shared VM that is on a server separate from the Cloud CPE Deployment Model server cluster.

    Figure 2 shows the architecture of the Contrail Cloud Platform nodes.

    Figure 2: Architecture of Contrail Cloud Platform Nodes

    Architecture
of Contrail Cloud Platform Nodes
    • The configure and control node hosts Contrail, OpenStack, and the VNFs. Contrail and OpenStack reside on the physical server and cannot be deployed in a VM. Each VNF resides in its own VM.
    • Each compute 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.

    The Contrail Service Orchestration Node supports multiple VMs:

    • The following components reside together in a shared VM:
      • Cloud CPE Tenant, Site and Service Manager
      • Identity and Access Manager
      • Logstash software
      • Network as a Service
      • Network Service Orchestrator
      • Server Sent Event
      • Service and Infrastructure Client
      • VNF Manager
    • The following components reside together in a shared VM:
      • Customer Portal
      • Kibana software
      • Network Service Designer and Customer Portal
      • Service and Infrastructure Client
    • Custom Contrail resides in a dedicated VM.
    • Junos Space Virtual Appliances and their associated databases:
      • If you use a standalone virtual appliance, one VM contains the Junos Space Virtual Appliance
      • If you use a Junos Space cluster for high availability, two VMs each contain a virtual appliance and two other VMs each contain associated databases
    • Two instances of Service and Infrastructure Monitor both reside in dedicated VMs.
    • The Service and Infrastructure Monitor Controller and the Load Balancer reside in a shared VM.

      These components work with the two instances of Service and Infrastructure Monitor to provider high availability of the software components.

    After you have installed and configured the hardware in the Cloud CPE Centralized Deployment Model, you run a deployment script to install and configure software components and VMs. Depending on the virtual environment, you may need to complete some manual configuration.

    Modified: 2016-02-01