At the recent Network Field Day 11, there were several discussions at the Cisco offices after the Cisco folks left the room. One of these discussions, led by Terry Slattery, was centered around SDN, and I think it’s worth a listen/watch (only about 20 minutes):
In this video, I made the argument that SDN should be limited to a very specific definition, which eliminates the management plane from the conversation entirely (around 5:40).
I am in full agreement that the term SDN, or “software-defined __ “ is at this point totally meaningless. It means so many things to so many different people, and predictably, this conversation ended with just as much confusion about SDN as when we started. So, to try to “define” SDN seems pointless, and smells of hair-splitting, but I do this for a very specific reason.
To me, SDN and network automation are two totally different things, yet they almost always get lumped together in conversations. Normally I wouldn’t try to remedy this, but since one of these things is a practical thing to do for many organizations, I want to offer up a different way of thinking about this.
First off, you do not have to go buy a shiny new product, or hire a bunch of developers, in order to improve network operations with automation. I am working with some good friends in the community to make this even more approachable to everyone. Network automation is not some lofty goal that only the top webscale companies have any business even looking at. This can (and should) be done at any scale. Because network automation isn’t just about speed.
Network automation is not just a technology, but more a methodology - a journey that anyone can and should embark on to improve network operations, regardless of scale.
To me, SDN is a very specific thing. It could be a product, or a project, but either way it is a very tactical idea. A tool to be used to solve a problem that frankly does not exist for many small-to-medium businesses. However, network automation is actually within our grasp because it’s something we can do ourselves, today, regardless of our organization’s size.
Do not assume that since you aren’t Google or Facebook that learning automation is not valuable. Many companies have development teams and/or are moving towards an in-house software development model, so now the right time to begin to build a more flexible, programmable infrastructure. Even if this is not the case, the vast majority of network problems in my experience have stemmed from either inconsistent configurations, or improper testing. Automation can and should help with both of these, regardless of scale.
Please, please, please, do not write off anything to do with automation because the vendors and the tech journalists have beaten the term “software-defined” to the point where it’s meaningless. There is some good stuff here, and you’d be best served to look into it.
I encourage you to reach out to me, or to some other great folks in the community (Jason Edelman, Scott Lowe, and many others) for any questions about how to get started. A lot of this stuff is within our grasp today.
I attended Network Field Day 11 as a delegate as part of Tech Field Day. Events like these are sponsored by networking vendors who may cover a portion of our travel costs. In addition to a presentation (or more), vendors may give us a tasty unicorn burger, warm sweater made from presenter’s beard or a similar tchotchke. The vendors sponsoring Tech Field Day events don’t ask for, nor are they promised any kind of consideration in the writing of my blog posts … and as always, all opinions expressed here are entirely my own. (Full disclaimer here)
- networking (20) ,
- sdn (49) ,
- software defined networking (3) ,
- software defined (1) ,
- network automation (2) ,
- automation (29)