Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

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

    NFV in the Cloud CPE Centralized Deployment Model

    The Cloud customer premises equipment (CPE) Centralized Deployment Model uses a microservice architecture, which is a distributed, non-hierarchical framework in which multiple software components—microservices—interact to perform the functions of the deployment. Each software component operates independently to implement a set of focused, related functions. The Cloud CPE Centralized Deployment Model uses the following software components for Network Functions Virtualization (NFV):

    • Contrail Cloud Platform, which provides underlying software-defined networking (SDN), NFV infrastructure (NFVI), and the virtualized infrastructure manager (VIM).
    • Contrail Service Orchestration, which provides a RESTful API to connect with service providers’ operational support systems (OSS) and business support systems (BSS) applications and is responsible for many management and network orchestration (MANO) activities in the deployment. Contrail Service Orchestration consists of the following components:
      • Administration CLI, which is a tool that you use to manage customers.
      • Cloud CPE Tenant, Site and Service Manager and its auxiliary component, Identity and Access Manager, which manage customers and map each customer’s network services to the appropriate gateway resources, such as the Layer 2 access interfaces and routing instances. These applications provide a northbound RESTful API to which you can connect OSS/BSS systems.
      • Customer Portal, which is an application that you can provide to customers to enable them to manage sites and services for their organizations through a graphical user interface (GUI). The Customer Portal application uses the RESTful API.
      • Network Service Designer, which enables design, creation, management, and configuration of network services through a GUI. Network services are stored in the network service catalog.
      • Network Service Orchestrator, which is responsible for ETSI-compliant management of the life cycle of network service instances. This application includes RESTful APIs that you can use to create and manage network service catalogs.
      • Service and Infrastructure Monitor, which works with Icinga, an open source enterprise monitoring system to provide data about the Cloud CPE Centralized Deployment Model, such as the status of virtualized network functions (VNFs), virtual machines (VMs), and physical servers; information about physical servers’ resources; components of a network service (VNFs and VMs hosting a VNF); counters and other information for VNFs; and software components running in Contrail Cloud Platform.
      • VNF Manager, which creates VNF instances and manages their life cycles.
    • Junos Space Virtual Appliance, which provides an element management system for Juniper Networks VNF.

    Figure 1 illustrates the software components and their interactions.

    Figure 1: Software Components of the Cloud CPE Centralized Deployment Model

    Software Components of the Cloud
CPE Centralized Deployment Model

    OSS/BSS applications and Contrail Service Orchestration components with OSS/BBS capabilities send requests to Network Service Orchestrator through its northbound REST API. Network Service Orchestrator then communicates through its southbound API to the Northbound API of the appropriate, directly connected, component. Subsequently, each component in the deployment communicates through its southbound API to the to the northbound API of the next component in the hierarchy. Components send responses in the reverse direction.

    The following process describes the interactions of the components when a customer requests the activation of a network service:

    1. Customers send requests for activations of network services through Customer Portal or OSS/BSS applications.
    2. Service and Infrastructure Monitor is continuously tracking the software components, hardware components, and processes in the network.
    3. Network Service Orchestrator receives requests through its northbound RESTful API and:
      • Accesses information about the network service and associated VNFs from their respective catalogs, and communicates this information to the VIM.
      • Sends information about the VNF to VNF Manager.
    4. The VIM and VNF Manager receive information from Network Service Orchestrator and:
      • The VIM creates the service chains and associated VMs in the NFVI provided by Contrail Cloud Platform. Contrail Cloud Platform creates one VM for each VNF in the service chain.
      • VNF Manager starts managing the VNF instances and, in the case of the vSRX, the Junos Space Virtual Appliance provides element management.
    5. The network service is activated for the customer.

    Modified: 2016-02-01