Jordan Martin has a problem. The idea of moving the control plane from a device to a central controller sounds like it makes a lot of sense in SDN. I mean, it’s called a control plane, why not move it to a controller? Despite the phonic similarity, this isn’t actually what happens.
Jordan takes the time to actually define what he means by the control plane, and shows why moving it to a controller makes the network less reliable and more inefficient. It’s an insightful breakdown of why something that seems common sense is much more problematic.
Jordan Martin comments:
One of the more popular misconceptions about SDN is that this new model of networking moves the control plane from a device to a controller. As much as it sounds like a network controller would be the control plane for a network, it simply isn’t true. For some, I believe this mistake is simply a lack of attention to terminology. For others, it’s a fundamental misunderstanding of the way that controller based networking works. Either way, it’s important that we, as network engineers, understand the concept as we move into the brave new world of orchestrated networks.
Read more at: Who Moved My Control Plane
- Cloud Extensions, DevOps Models, and Playing with GUIs on Docker with Gestalt Cloud News 17.6 - June 22, 2017
- AMD’s Future in Servers: New 7000-Series CPUs Launched and EPYC Analysis - June 22, 2017
- PCIe versus Ethernet in a Composable System - June 22, 2017
- Managing Your IT Career – The On-Premise IT Roundtable - June 20, 2017
- Wavebox: All Your Web Apps Are Belong To Us - June 16, 2017
- Excelero’s NVMesh Magic - June 14, 2017
- A Quick Look at LinuxKit Packaging System - June 14, 2017
- Advice to Vendors: Know Your Identity - June 9, 2017
- QNX Gets Containers - June 8, 2017
- Datera Elastic Data Fabric - June 7, 2017