Ciena picks ONAP’s policy code to enhance Blue Planet
Operators want to use automation to help tackle the growing complexity and cost of operating their networks.
Kevin Wade“Policy plays a key role in this goal by enabling the creation and administration of rules that automatically modify the network’s behaviour,” says Kevin Wade, senior director of solutions, Ciena’s Blue Planet.
Incorporating ONAP code to enhance Blue Planet’s policy engine also advances Ciena’s own vision of the adaptive network.
Automation platforms
ONAP and Ciena’s Blue Planet are examples of network automation platforms.
ONAP is an open software initiative created by merging a large portion of AT&T’s original Enhanced Control, Orchestration, Management and Policy (ECOMP) software developed to power its own software-defined network and the OPEN-Orchestrator (OPEN-O) project, set up by several companies including China Mobile, China Telecom and Huawei.
ONAP’s goal is to become the default automation platform for service providers as they move to a software-driven network using such technologies as network functions virtualisation (NFV) and software-defined networking (SDN).
Blue Planet is Ciena’s own open automation platform for SDN and NFV-based networks. The platform can be used to manage Ciena’s own platforms and has open interfaces to manage software-defined networks and third-party equipment.
Ciena gained the Blue Planet platform with the acquisition of Cyan in 2015. Since then Ciena has added two main elements.
One is the Manage, Control and Plan (MCP) component that oversees Ciena's own telecom equipment. Ciena’s Liquid Spectrum that adds intelligence to its optical layer is part of MCP.
The second platform component added is analytics software to collect and process telemetry data to detect trends and patterns in the network to enable optimisation.
“We have 20-plus [Blue Planet] customers primarily on the orchestration side,” says Wade. These include Windstream, Centurylink and Dark Fibre Africa of South Africa. Out of these 20 or so customers, one fifth do not use Ciena’s equipment in their networks. One such operator is Orange, another Blue Planet user Ciena has named.
A further five service providers are trialing an upgraded version of MCP, says Wade, while two operators are using Blue Planet’s analytics software.
In a closed-loop automation process, the policy subsystem guides the orchestration or the SDN controller, or both, to take actions
Policy
Ciena has been a member of the ONAP open source initiative for one year. By integrating ONAP’s policy components into Blue Planet, the platform will support more advanced closed-loop network automation use cases, enabling smarter adaptation.
“In a closed-loop automation process, the policy subsystem guides the orchestration or the SDN controller, or both, to take actions,” says Wade. Such actions include scaling capacity, restoring the network following failure, and automatic placement of a virtual network function to meet changing service requirements.
In return for using the code, Ciena will contribute bug fixes back to the open source venture and will continue the development of the policy engine.
The enhanced policy subsystem’s functionalities will be incorporated over several Blue Planet releases, with the first release being made available later this year. “Support for the ONAP virtual network function descriptors and packaging specifications are available now,” says Wade.
The adaptive network
Software control and automation, in which policy plays an important role, is one key component of Ciena's envisaged adaptive network.
A second component is network analytics and intelligence. Here, real-time data collected from the network is fed to intelligent systems to uncover the required network actions.
The final element needed for an adaptive network is a programmable infrastructure. This enables network tuning in response to changing demands.
What operators want, says Wade, is automation, guided by analytics and intent-based policies, to scale, configure, and optimise the network based on a continual reading to detect changing demands.
Colt's network transformation
Colt's technology and architecture specialist, Mirko Voltolini, talks to Gazettabyte about how the service provider has transformed its network from one based on custom platforms to an open, modular design.
It was obvious to Colt that something had to change. Its network architecture based on proprietary platforms running custom software was not sustainable; the highly customised network was cumbersome, resistant to change and expensive to run. The network also required a platform to be replaced - or at least a new platform added alongside an existing one - every five to seven years.
Mirko Voltolini
"The cost of this approach is enormous," says Mirko Voltolini, vice president technology and architecture at Colt Technology Services. "Not just in money but the time it takes to roll out a new platform."
Instead, the service provider has sought a modular approach to network design using standardised platforms that are separated from each other. That way, a new platform with a better feature set or improved economics can be slotted in without impacted the other platforms. Colt calls its resulting network a modular multi-service platform (MSP).
The MSP now delivers the majority of Colt's data networking and all-IP services. These includes Carrier Ethernet point-to-point, hub-and-spoke and private networks services, as well as internet access, IP VPNs and VoIP IP-based services.
The vendors chosen for the MSP include Cyan with its Z-Series packet-optical transport system (P-OTS) and Blue Planet software-defined networking (SDN) platform and Accedian Networks' customer premise equipment (CPE). Cyan's Z-Series does not support IP, so Colt uses Juniper Networks' and Alcatel-Lucent's IP edge platforms. Colt also has a legacy 20-year-old SDH network but despite using a P-OTS platform, it has decided to leave the SDH platform alone, with the modular MSP running alongside it.
Colt chose its vendors based on certain design goals. "The key was openness," says Voltolini. "We didn't want to have a closed system." It was Cyan's management system, the Blue Planet platform, that led Colt to choose Cyan.
Associated with Blue Planet is an ecosystem that allows the management software to control other vendors' platforms. Cyan uses 'element adapters' that mediate between its SDN interface software and the proprietary interfaces of its vendor partners. Cyan says that its Z-Series P-OTS appears as a third-party piece of equipment to its Blue Planet software in the same way as the other vendors' equipment are; a view confirmed by Colt. "Because of its openness, we have been able to integrate other vendors to use the same management system as if they were Cyan components," says Voltolini.
"Cyan was probably the best option available and we decided to go with it," says Voltolini. The company was looking at what was available two years ago and Voltolini points out that the market has evolved significantly since then. "In the end, if you want to move ahead, you need to make decisions," he says. "We are quite happy with what we have picked and we continue to improve it."
Colt says that as well as SDN, network functions virtualisation (NFV) is also important. "With the same modular platform we have created a virtual component which is a layer-3 CPE," says Voltolini. The company is issuing a request-for-information (RFI) regarding other CPE functions like firewalls, load-balancers and other networking components.
Benefits and lessons learned
Adopting the MSP has speeded up Colt's service delivery. Before the modular network, it would take between 30 and 45 days for Colt to fulfil a customer's request for a three-month-long Ethernet link upgrade, from 100 Megabit to 200 Megabit. Now, such a request can be fulfilled in seconds. "We didn't need any more layer-3 CPE and we can upgrade remotely the bandwidth," says Voltolini.
Colt also estimates that it will halve its operational costs once the new network is fully deployed; the network went live in November 2013 and has not been deployed in all locations. The operational expense improvement and the greater service flexibility both benefit Colt's bottom line, says Voltolini.
A key lesson learned from the network transformation is the importance of leading staff through change rather than any technological issues. "The technology has been a challenge but in the end, with the suppliers, you can design anything you want if you have the right level of collaboration," says Voltolini. "But when you completely transform the way you deliver services, you are touching everything that is part of the engine of the company."
Colt cites aspects such as engineering solutions, service delivery, service operations, systems and processes, and the sales process. "You need to lead the transition is such a way that everybody is going to follow you," says Voltolini.
Colt encountered obstacles created because of the staff's natural resistance to change. "Certain things took longer," says Voltolini. "We had to overcome obstacles that weren't really obstacles, just people's fear of change."
The art of virtualised network function placement
Cyan is delivering its Blue Planet NFV orchestrator software that will make use of enhancements being made to OpenStack developed by Red Hat in close collaboration with Telefónica.
Gazettabyte asked Nirav Modi, director of software innovations at Cyan, about the work.
Q: The concept of deterministic placement of virtualised network functions. Why is this important?
NM: We are attempting to solve a fundamental technology challenge required to make NFV successful for carriers. Telefónica has been doing a lot of internal trials and its own NFV R&D and has found that the placement of virtualised network functions greatly affects their performance.
We are working with Telefónica and Red Hat to solve this problem, to ensures virtualised network functions perform consistently and at their peak from one instance to another. This is particularly important for composite or clustered virtualised network function architectures, where the placement of various components can affect performance and availability.
Also, you need to ensure that the virtualised network functions are located where the most suitable compute, storage or networking resources are located. Other important performance metrics that need to be considered include latency and bandwidth availability into the cloud environment.
What is involved in enabling deterministic virtualised network functions, and what is the impact on Cyan's orchestration platform?
Deterministic placement requires an orchestration platform, such as Cyan’s Blue Planet, to be aware of the resources available at various NFV points of presence (PoPs) and to map operator-provided placement policies, such as performance and high-availability requirements, into placement decisions. In other words, which servers should be used and which PoP should host the virtualised network function.
For the operator, interested in application service-level agreements (SLAs) and performance, Cyan’s orchestration platform provides the intelligence to translate those policies into a placement architecture.
Does this Telefonica work also require Cyan's Z-Series packet-optical transport system (P-OTS)?
NFV is all about taking network functions currently deployed on purpose-built, vertically-integrated hardware platforms, and deploying them on industry-standard commercial off-the-shelf (COTS) servers, possibly in a virtualised environment running OpenStack, for example.
In such an set-up, Cyan’s Blue Planet orchestration platform is responsible for the deployment of the virtualised network functions into the NFV infrastructure or telco cloud. Cyan’s orchestration software is always deployed on COTS servers. There is no dependency on using Cyan’s P-OTS to use the Blue Planet software-defined networking (SDN) and NFV software.
The Z-Series platform can be used in the metro and wide area network to enable a scalable and programmable network. And this can supplement the virtual network functions deployed in the cloud to replace existing hardware-based solutions, but the Z-Series is not involved in this joint-effort with Telefónica and Red Hat.