AzureStack breakdown of Network Controller
Now I’ve previously blogged about some of the other networking component in AzureStack (Software Load Balancing) and Distributed Firewall which are essential components on how we can achieve a software-defined network. Now both the dfW and SLB are just components that operate in the data plane, but would not be possible without a central component which lies in the control plane, namely the Network controller.
Now for those that haven’t heard about it yet, it is a new role in Windows Server 2016 which is in essence a centrally component to manage the infrastructure network. From an AzureStack perspective, when we go in and configure a Network Security Group or a load balancing IP address, or either by usingPowerShell scripts, or System Center Virtual Machine Manager (SCVMM) it programs network policy through the RESTful API exposed by the Microsoft Network Controller. The Network Controller then distributes this policy to each of the Hyper-V hosts using the OVSDB Protocol and a set of schemas to represent virtual networks, ACLs, user-defined routing, and other policy to the virtual network.
Another critical piece of this SDDC is the new Software Defined Network (SDN) Stack which the Hyper-V Virtual Switch using the Azure Virtual Filtering Platform (VFP) Switch Extension, which is also controlled by the Networking Controller.
Read the entire article here, AzureStack breakdown of Network Controller
via Marius Sandbu.