A few weeks ago, I wrote about where I was in the world of programming. As I said then, I am still focused on building a onePK application. This onePK application now dubbed Network Control Manager is a central interface to the network. It can be used to gather real time data as well as make changes to the network in a more centralized, automated, and real-time fashion. Following the SDN model, this application can be seen as a SDN controller if you wish to call it that. The southbound API used is Cisco’s onePK and the northbound API is self-defined as “je-nb-API” :). The application/controller exposes northbound RESTful interfaces to be consumed by 3rd party applications and control programs, the first of which is a CLI application that interacts with the network via Network Control Manager.
Network Control Manager - Architecture
This CLI application is a central CLI for the complete network. Gone should be the days of logging into each device. Imagine needing to gather specific data from 20, 30, or even 100 nodes on the network? Maybe it’s a serial number, maybe it’s looking at neighbors on a certain link, etc. Whatever it maybe, the traditional ways have been tedious because the network is viewed as a collection of independent network elements. Shout out to Nitin Khanna who helped with the first version of the CLI Python application!
There have been failed attempts to deploy fancy GUIs and dashboards that network admins just don’t get in the habit of using. Network Control Manager is an attempt to have a central console, a central CLI for the network. Based on the architecture, the same APIs used for the CLI application can be leveraged to build a fancy GUI. Another avenue currently being explored rather than CLI or GUI is the implementation of PowerShell or PowerCLI-like cmdlets to bring the power of enhanced programmability to the network without a full blown CLI, etc. It’s still the early days for these types of unified network programmability/data collection applications, especially this one, so there is much more that can be done with due time.
When I first set out to build a onePK application, my goals were pretty straight forward. They were as follows:
The outcome is Network Control Manager. Hopefully this intrigued you enough to want to learn more.
There have been failed attempts to deploy fancy GUIs and dashboards that network admins just don’t get in the habit of using. Network Control Manager is an attempt to have a central console, a central CLI for the network. Based on the architecture, the same APIs used for the CLI application can be leveraged to build a fancy GUI. Another avenue currently being explored rather than CLI or GUI is the implementation of PowerShell or PowerCLI-like cmdlets to bring the power of enhanced programmability to the network without a full blown CLI, etc. It’s still the early days for these types of unified network programmability/data collection applications, especially this one, so there is much more that can be done with due time.
When I first set out to build a onePK application, my goals were pretty straight forward. They were as follows:
- Improve operational efficiencies of all types of networks, not just DC. WAN, LAN, etc.
- Reduce box by box management
- De-couple the CLI and mgmt from individual network elements
- Offer CLI and GUI to interact the network without changing the application
- Focus first on retrieving data to ease the fear of admins with “programming” the network (although this app can make changes too)
The outcome is Network Control Manager. Hopefully this intrigued you enough to want to learn more.
For a DEMO and short overview, take a look at this video.
For a deeper look and complete OVERVIEW of Network Control Manager, please take a look at this one.
And here is a basic slide show (no video)...
Thanks,
Jason
Twitter: @jedelman8
RSS Feed
