I’ve been using the phrase “SDN consumability” here and there of late, assuming that there was nothing particularly revolutionary in the idea. The response, however, is typically a cocked head, an interested look, and a question: “What do you mean by that?”
So here’s what I mean by that:
In order for SDN to see mainstream adoption, SDN solutions need to be/have
- Simple to operate – easy to deploy, low-to-moderate learning curve
- Safe and reliable – tech is stable, nothing blows up, no one gets fired
- No blue-sky requirements, limited DIY – tech and process migration support available
Yes, I’m crazy enough to get up early on a Sunday to go to an SDN conference. I won’t say that there was a lot of “new news” in this session yesterday, but it certainly validated a number of hypotheses. I wound up taking many pages of notes even so, and I’ll summarize the main themes and highlights here.
Open Source and Standards Bodies
While it shouldn’t be a surprise at the Open Networking Summit to hear attendees and speakers beat the open source drum, it was interesting how completely dismissive of traditional vendor implementations most of the speakers were. Prodip Sen of Verizon, also Chair of the ETSI NFV group, commented matter-of-factly,
“Open source is the new standards body. Equipment manufacturers need to build openness, interoperability and modularity into their products. We’re not interested in vertically integrated stacks—that day is gone.”
I could caveat that by noting that even the “enterprise” speakers (from Ebay/Paypal) were rather Web 2.0-flavored and so not completely representative of the broad mass of non-tech enterprises and their needs, but the general direction is pretty unmistakable.