The notion of network programmability is a key concept of SDN, but as usual, the devil is in the details.
At present there’s a lot of discussion around intent modeling, promise theory, and abstractions, but how do you take a business or application requirement (the network should do X) and turn it into actual device settings that will deliver this requirement?
On today’s sponsored podcast from Apstra, we look at how their distributed network operating system, AOS, enables business intent to be translated into a vendor-agnostic network configuration. Apstra has a new approach to designing and running networks for higher availability and lower cost.
Our guests are CTO and cofounder Sasha Ratkovic; and Derick Winkworth, Apstra’s bit-wrangling telepath (yup, that’s what it says on LinkedIn).
We’ll drill into specifics on Apstra’s network OS, just what is meant by “intent”, and how you go from high-level requests to actually implementing complete network configurations via automation.
From there, we’ll explore how Apstra enforces your intent. After all, cables come unplugged, routing adjacencies fail, and cowboys create configuration chaos. Configuration automation is great, but only if the configuration stays in place once deployed.