Chapter 9: Consuming Controllers and High-Level Networking APIs with requests
Why do we have to always connect to each of our devices individually to carry out some operation? This is a question you might have asked yourself throughout this book. And while device-by-device configuration remains a common way to interact with networking device configuration, controller-based approaches, where a central component coordinates and controls all devices on a network, are on the rise. And these control components usually offer us an application programming interface (API) that we can use to interact with the controller. The controller then goes out to all the devices we have registered on it and retrieves the required information or applies the required configuration change, without us having to explicitly apply this configuration change to all our devices. The controller takes over the job of connecting to each of the devices.
The common architectural style these APIs use is REST, short...