Introduction

Software Defined Networking, SDN, has become a very broad term, inclusive of a wide range of design solutions, most simply sharing the commonality to build open networks implementing concepts native to abstraction and programmability. It can be rather overwhelming to digest all aspects of SDN at once, but where I’ve seen the best business value to effort ratio is by focusing on just one facet; Service Automation. In the most visionary sense, Service Automation provides the inherit intelligence necessary to support unattended network creation, operation and remediation tasks.

However, just as no two customers are ever truly the same, no two networks are ever truly the same; Each customer and each network must plot their own unique digital roadmap to navigate from present to future capabilities. For the past year, I have been presenting this transformation vision across the service provider and large enterprise landscape, and almost every time I am challenged with the same question;

Where do I start?

In order to answer this question, I take the approach of using a maturity model. In this model I have identified common building blocks and put them together, in conjunction with specific technologies, to develop a maturity roadmap. Through assessment of each position in the roadmap, one can measure transformation progress, while also gaining an understanding of how best to accelerate and promote maturity advancement.

The First Step: SDN Controller

The first building block towards Service Automation maturity is the introduction of a SDN Controller platform. I advocate for solutions based on OpenDaylight (ODL), a Linux Foundation sponsored and community driven project. ODL provides a good basis for control plane functions, not only because it’s open, but because it has mature Netconf, OpenFlow and BGP implementations. In addition to these protocols, which are commonly used to achieve data plane programming, ODL also provides a fundamental YANG abstraction engine capable of simplifying integrations. If you have not implemented a directional SDN controller, then I believe you are still at the best effort stage of maturity, either locked into a vendor proprietary system, suffering from a proliferation of third party systems, or not using any directional systems to manage your network creation, operations and reconciliation interactions.

CLI EliminationWith a Controller in place, management services can be migrated away from legacy methods, towards the pillar concepts of SDN. Thus, the second building block towards Service Automation maturity is the concept of CLI elimination. Where network system or process solutions are still dependent upon connecting directly to each network element and issuing commands through a terminal type interface, the Controller will now provide a middle-ware function, unifying access to all network elements through a single converged interface. The simplicity created by this convergence supports an operational DevOps mentality, where device interactions can now either be manually scripted or controlled through a simple workflow interface.

AbstractionWith CLI access eliminated, the third building block towards Service Automation maturity is the concept of abstraction. Where device interactions have now been converged, abstraction standardizes these interactions across any equipment vendor and any product family. This creates a common language supported by a single northbound interface, making system, vendor or product OAM tasks significantly less complex. This drives efficiencies in device interactions, reducing the mighty time to revenue, and creates leverage in capital expenses negotiations, by breaking vendor lock in. Using abstraction to simplify device interactions is considered the entry point for software defined networking. If you have already reached a semi-automated state of maturity, congratulations, you are running a software defined network.

OrchestrationThe fourth building block towards Service Automation maturity is the concept of end to end orchestration. Where device interactions are now converged and standardized into a single interface, reliable integration with a directional workflow orchestrator can be achieved. Given changes made to the device base are now abstracted by the Controller, significant OpEx reduction can be realized through one-time orchestration on-boarding, breaking the loop of continuous on-boarding effort. Combining the benefits of CLI elimination and abstracted device interactions, with the end to end capabilities of directional orchestration, results in a true closed-loop environment. If you have reached this fully automated state of maturity SDN is no longer just a technical concept but has demonstrated significant business value.

ProgrammabilityThe fifth and final building block towards Service Automation maturity, and by the far the hardest and more disruptive, is the concept of control plane dis-aggregation and remote data plane programming. Where device interactions, via configuration, have now been fully automated, this final step shifts data plane decisions from the local device, to the centralized Controller, using a combination of Openflow, BGP and even P4 protocols. Tasks such as path computation, security micro segmentation, operational self healing and real-time service operations can be accomplished through integrations with third party systems providing machine learning and artificial intelligence capabilities. In the center of all this action is the SDN controller, now fully intelligent and self-aware, completing the roadmap from legacy networking to intent driven networking.

Conclusion

The maturity roadmap, and associated recommendations, are the result of my experiences implementing solutions in the real world, combined with thought leadership borrowed from other technical community leaders. Although there is certainly other ways to measure maturity, and alternative roadmaps on how to achieve each transformation step, all players in this space have one common goal: to improve the quality of network service delivery. To which I ask;

How mature is your transformation? 

A realistic assessment of the market would suggest that very few have reach a truly automated state, while self driving remains a conceptual objective only. If you find yourself somewhere in the middle, you most likely have figured all this out and are on your way, you probably do not need help. However, if you are still operating in a best effort manner, if you have read this article and are thinking “I’m at step 0” — reach out and lets talk about how I can help drive maturity in your network.

[Bazillasoft LLC – Copyright 2018 – All Rights Reserved]