Features Supported in This Release

• Administration Portal—Contrail Service Orchestration now includes an Administration Portal that you can use to perform administrative tasks for the Cloud CPE Centralized Deployment Model, such as:
  • Configuring the virtualized infrastructure manager (VIM).
  • Configuring points of presence (POPs).
  • Configuring the element management system (EMS) for the VNFs.
  • Configuring resources and virtual networks used by Network Service Orchestrator and Contrail Cloud Platform for orchestrating network services.
  • Adding a new customer, adding an administrator at the customer enterprise who activates and manages network services, and adding customer sites.
  • Allocating network services to customers.
• Direct Access to the Internet from Sites—You can now configure direct access to the Internet for sites in a customer’s network. Sites can also connect to the Internet through the customer’s VPN. Sites can connect to the Internet through either or both of these topologies. You can activate network services on any connection in these topologies.
• Support for multiple VIMs—The Cloud CPE Centralized Deployment Model now supports multiple VIMs to enable use of a dedicated VIM in a specific regional POP. This feature optimizes performance and enables scaling of the deployment model. A single instance of Contrail OpenStack, as part of a dedicated Contrail Cloud Reference Architecture (CCRA) installation, provides the VIM for the region, and all VIMs share a single OpenStack Keystone in the central POP. Contrail Service Orchestration in the central POP the provides management and orchestration for all regions of the network and communicates with the OpenStack Keystone. You configure multiple VIMs with the Cloud CPE Centralized Deployment Model installer and its associated configuration file.
• Support for Contrail Service Orchestration high availabilty—You can install the Cloud CPE Centralized Deployment Model with high availability for Contrail Service Orchestration. This installation includes two Contrail Service Orchestration nodes on different servers in the central CCRA. Each of these nodes hosts instances of the Contrail Service Orchestration components and if a component on the primary node fails, the corresponding component on the secondary nodes takes over. Contrail Service Orchestration high availability provides resiliency for the graphical user interfaces (GUIs), APIs, and the NFV management and orchestration (MANO) processes. You can still use a non-redundant Contrail Service Orchestration configuration if you prefer. in either case, Contrail Service Orchestration in the central POP the provides management and orchestration of network services in all regional POPs.
• Deployment on a Contrail OpenStack instance configured for high availability—The installer for the Cloud CPE Centralized Deployment Model now enables installation of the deployment model on a Contrail OpenStack instance configured for high availability. This configuration includes three redundant Contrail configure and control nodes in a CCRA, and provides resiliency for VIMs, VNFs, and network services.
• Support for new VNFs—The Cloud CPE Centralized Deployment Model now supports the Cisco Cloud Services Router 1000V Series (CSR-1000V) firewall VNF.
• Monitoring network services in Customer Portal—End users can now monitor information about active network services in their network by linking directly to Service and Infrastructure Monitor from Customer Portal.
• Configuration of VNFs in Network Service Designer and Customer Portal—The graphical user interface (GUI) for configuring VNFs has changed and you can now configure additional settings for some VNFs.
• Configuration of Syslog servers for vSRX VNF instances—You can now configure Syslog servers for vSRX VNFs instances in Network Service Designer and Customer Portal.
• Introduction of the MX Series router as a physical network element (PNE)—The Cloud CPE Centralized Deployment Model now supports the MX Series router as a PNE. Configuration of the PNE in Contrail Service Orchestration simplifies provisioning of the physical device through automation. Combining provisioning and configuration for PNEs and VNFs provides end-to-end automation in network configuration workflows. You configure the PNE in Administration Portal.
• VNF resiliency—If a network service becomes unavailable due to a connectivity issue with a VNF, Network Service Orchestrator maintains existing instances of the network service in end users’ networks and initiates recreation of the VNFs. During this recovery process, the end user cannot activate the network service on additional network links. When the problem is resolved, normal operation resumes and end users can activate the network service on additional network links.

Tested Hardware and Software

The Cloud CPE Centralized Deployment Model has been tested with:

• The network devices described in Table 1
• The servers described in Table 2
• The software described in Table 3

Minimum Hardware and Software Requirements for the Servers and VMs

The Cloud CPE Centralized Deployment Model runs on commercial off-the-shelf (COTS) x86 servers. When obtaining servers for the Cloud CPE Centralized Deployment Model, we recommend that you:

• Select hardware that was manufactured within the last year.
• Ensure that you have active support contracts for servers so that you can upgrade to the latest firmware and BIOS versions.

Table 4 shows the required hardware specification for servers you use in the Cloud CPE Centralized Deployment Model.

Table 5 lists the software requirements for the servers.

Table 7 shows complete details about the VMs required on the Contrail Service Orchestration nodes on server 1 and server 2 for a redundant Contrail Service Orchestration configuration.

Table 8 lists the requirements for the VM for the installer. You need to create this VM on the Contrail Service Orchestration node if you create and configure the Contrail Service Orchestration VMs manually. You must create and configure the VMs manually if you use a supported hypervisor other than KVM on the on the Contrail Service Orchestration node. In addition, if you want to use VMs that you already created, you must configure them manually.

If you use the provisioning tool to create and configure the VMs, you deploy the installer directly on the Contrail Service Orchestration node. You can use the provisioning tool if you use the KVM hypervisor on a Contrail Service Orchestration node.

Accessing GUIs

Access to the GUIs for the Cloud CPE Centralized Deployment Model depends on whether you use a non-redundant or a redundant Contrail Service Orchestration Installation. Table 9 shows the URLs and login credentials for the GUIs for a non-redundant Contrail Service Orchestration installation.

Table 10 shows the URLs and login credentials for the GUIs for a redundant Contrail Service Orchestration installation.

Licensing

You must have licenses to download and use the Juniper Networks Cloud CPE Centralized Deployment Model. When you order licenses, you receive the information that you need to download and use the Cloud CPE Centralized Deployment Model. If you did not order the licenses, contact your account team or Juniper Networks Customer Care for assistance.

Cloud CPE Centralized Deployment Model licensing includes licenses for Contrail Service Orchestration and Contrail Cloud Platform. The Cloud CPE Centralized Deployment Model licenses are based on VNF capacity, which also determines the number of separate Junos Space Network Management Platform licenses required. See Table 11.

Individual Contrail Service Orchestration licenses and Contrail Cloud Platform licenses can be purchased separately. Contrail Service Orchestration licenses are also based on VNF capacity.

You will also need licenses for the MX Series router, EX Series switch, and QFX Series switch.