Cross Provisioning Platform Overview
The Cross Provisioning Platform (CPP) software provides a real-time, operations support system (OSS) for creating and deploying multi-vendor LAN/WAN services.
Creating services for Cross Provisioning Platform deployment requires the coordination of tasks performed in several areas of expertise including script design, system administration, and service provisioning.
Junos Space Release 13.1P1 includes software modules that manage the essential interaction between the Juniper Networks devices and the devices of other vendors for which the Cross Provisioning Platform service will be deployed.
The CPP software manages the interaction of a module called the Service Activation Director (SAD) with a module called the Service Aware Manager (SAM). The scripts that pertain to Juniper Networks devices are managed by the SAD. Scripts imported into the system that pertain to the outside vendor device are managed by the SAM. Another type of script renders the graphical user interface (GUI) page that enables a service provisioner to configure the devices for the service.
Before you use Junos Space to provision a service definition upon which to base the service order, you must import several required scripts to the system.
An important aspect of creating a Cross Provisioning Platform service definition is using Cross Provisioning Platform to attach the required scripts to the definition. When you create the Cross Provisioning Platform service definition, you attach scripts designed for the service for both the SAM and SAD. The CPP software in Junos Space manages the information that defines the service for the outside vendor device and the information that defines the service for the Juniper Networks device.
Juniper Networks script designers create the scripts that provide required information for the Juniper Networks devices. Script designers for the outside vendor must create scripts that provide required information for their devices. The scripts for Juniper Networks devices and third-party devices are all managed by the script manager in the CPP software.
To enable Cross Provisioning Platform, script designers create the following three types of scripts and upload them to the local file system.
Junos XSLT—Provides the code that enables provisioning a particular Juniper Networks device.
SAM XSLT—Provides the code that enables provisioning the device of another vendor.
A system administrator adds the scripts into the local file system using the Junos Space Cross Provisioning Platform application. Thereafter, the service provisioner uses Cross Provisioning Platform to attach the scripts to the service definition and service order.
The GUI scripts generate high level service data with service topology embedded. The transformation code in the CPP software compiles high-level service data into low-level configuration data, which is pushed to the network devices.