Managing Connectivity Services in a Multi-vendor Network
Jun 8, 2015
In a previous post, we learnt about Junos Space applications for managing services of different types, across the network stack.
With the growing interest in SDN/NFV, it is becoming increasingly important that management systems are able to manage multi-vendor networks. So, how does Junos Space handle services in a multi-vendor environment?
Junos Space Cross Provisioning Platform (or, CPP) is one of several solutions that address this important requirement. CPP is a Junos Space application that is built using the Junos Space SDK and RESTful web services infrastructure to essentially turn Junos Space into a ‘Manager of Managers’.
CPP sits above the service activation framework (provided by Connectivity Services Director) to automate L2/L3 service provisioning on Juniper devices. In addition to this, CPP also implements an adapter that allows it to communicate with an Alcatel Lucent SAM 5620 management system over the SAM-O interface. This adapter enables CPP to push service configuration down to Alcatel Lucent devices via the SAM 5620 platform. In essence, CPP is able to provision services across multi-vendor devices – Juniper and Alcatel Lucent, through their respective management applications and hence functions like a “Manager of Managers”.
What value does CPP deliver beyond merely provisioning services between Juniper and Alcatel Lucent gear? Huge - if you consider the challenges that service providers face while introducing new services in their network.
Service providers who need to provision services in a multi-vendor environment face multiple challenges, including:
Tying together Element/Network Management Systems (EMS/NMS) from different vendors and orchestrating services across a multi-vendor network.
Quickly reacting to customer needs to deliver new services
Troubleshooting and maintaining services in a multi-vendor network
Traditional IT platforms such as Operations/Business Support Systems (OSS/BSS) are typically customized to meet a service provider’s specific service provisioning needs. These platforms and IT projects require huge upfront CapEx investments. Implementing a new service, or tweaking a small feature in an existing service profile, is an expensive investment in time and resources and typically takes several months to implement. With such lead times, by the time a service is implemented, it may no longer be relevant.
CPP provides a “one-size-fits-all” solution that disrupts the existing IT model by enabling service providers to quickly design and deploy new services in a multi-vendor network with minimal financial overhead.
CPP uses a script-based approach to provision services through the Flex Services framework, which facilitates flexible service creation and design without requiring a complicated software development cycle. Complex configurations such as QoS, firewall policies and business logic can be easily accommodated through the use or predefined scripts that allow network operators to:
Create a data model for a new service
Create a user interface to provision the service
Define business logic for deploying the new service on Juniper and non-Juniper devices
Implement complex workflows that provide orchestration and service chaining functionality
CPP can be used to manage the service lifecycle, which consists of device and service discovery, service creation, modification, troubleshooting and finally decommissioning. Its flexible service scripting framework also opens up interesting applications in service orchestration, service chaining and automation.