In part 1, we provided a sneak preview into Open NX-OS and demoed a few programmability and automation capabilities to help you build and manage networks simpler and quicker. In this session network programmability, we’ll cover in detail the NX-API REST (Object Model), NX-Toolkit, and more of NX-API. See how the power of Object Model/NX-API REST used in ACI is used with Open NX-OS to provide an advanced framework for network control and true programmability — allowing organizations to accelerate the DevOps model approach and respond more quickly to business demands.
So what is NX-API REST all about? First we need to understand the challenge today. As data center networks become more virtualized and move toward cloud and agile IT models, managing these networks through CLI or other means doesn’t allow for operating the infrastructure as a single system. This is no longer sufficient.
NX-API REST exposes functions as a series of objects and their attributes. At its foundation, this provides an architecture for programmability.
The NX-Toolkit is a set of python libraries that allow basic configuration of the Cisco Nexus Switch. It is intended to allow users to quickly begin using the REST API, and accelerate the learning curve necessary to begin using the switch. Instead of having to manually create the objects, we can use NX-Toolkit to abstract this (i.e. automatically create objects for us). All we need to do is call a function.
The NX-API capability allows you to send and receive commands over HTTP to a remote switch, and get the result of those commands in the JSON format. This format makes it very easy to understand, and especially to script. Screen scraping is not necessary.
Sign up below and we will see you at the Cisco September 25th DemoFriday on network programmability.
Don’t sweat it if you can’t make it to the live event. Register below and we will let you know when all of the assets from the live event are available so you can enjoy them at your convenience.