Your browser failed to load CSS style sheets. Your browser or web proxy might not support elliptic-curve TLS

Building network automation solutions

9 module online course

Start now!
back to overview

As Expected: Where Have All the SDN Controllers Gone?

Roy Chua (SDx Central) published a blog post titled “Where Have All the SDN Controllers Gone” a while ago describing the gradual disappearance of SDN controller hype.

No surprise there - some of us were pointing out the gap between marketing and reality years ago.

It was evident to anyone familiar with how networking actually works that in a generic environment the drawbacks of orthodox centralized control plane SDN approach far outweigh its benefits. There are special use cases like intelligent patch panels where a centralized control plane makes sense. There are applications like traffic engineering where central visibility (but not centralized control plane) makes sense. There are environments where treating the whole network as a single box is acceptable (see also: Juniper’s Virtual Chassis Fabric). Is that good enough to support multiple controller ecosystems? Obviously not - in most cases, automation and abstraction give you better results without having to deal with a newly-reinvented wheel.

Then there are the hardware challenges. Early SDN controllers tried to push a square peg into a round hole and failed miserably or required a vertically-integrated stack that defied the whole idea of the original SDN religion (as opposed to what $vendor marketers made out of the term).

Controllers that were designed to do useful work in real-life networks like Faucet have limited Hardware Compatibility List - once you figure out all the OpenFlow functionality you need to get the job done, you realize there are only a few switches on the market that have it all.

Finally, there’s the Open Daylight’s kitchen sink approach turning what might have been a potentially interesting platform into a quagmire of dependencies that could do things like HTTP-to-BGP-LS or HTTP-to-NETCONF protocol translation - obviously not enough to survive.

Now that the last vestiges of SDN controller hype are fading, we might start considering solutions that solve actual production challenges instead of fueling vendor marketing machinery. Like always, it took us almost a decade to wake up from unicorn dust induced haze. We never learn from past mistakes, do we?

If you’re interested in how Nick Buraglio uses Faucet in production networks, listen to Episode 101 of Software Gone Wild.

Please read our Blog Commenting Policy before writing a comment.

1 comment:

  1. It seems like the whole networking industry is still a buyer market. Lucky you!

    ReplyDelete

Constructive courteous comments are most welcome. Anonymous trolling will be removed with prejudice.

Sidebar