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.