In my previous post, Network Virtualization Part 1, I talked about some fundamental differences between server virtualization and network virtualization. The focus was how VMware created a hypervisor for server virtualization and how they created a network operating system for network virtualization. Now I will focus on some other properties that should be included in network virtualization --- to enable these properties could mean features and functions in both the virtual and physical networks.
This post compares high level concepts of server virtualization and network virtualization. There are benefits as we know them today for each, but it is just the beginning for network virtualization. The model we see in the future may very well be completely different than what it looks like today, but at the very least overlays will be around for quite some time given the amount of industry momentum. I’ll also give my thoughts and speculate on things I’d like to see from the vendors in this space.
In follow up posts, I hope to give more examples of how the physical network should adapt to help optimize the virtual network.
I haven’t been blogging as much as I’d like – maybe that will always be the case. It’s hard finding the time with a day job and when each post takes planning, writing, editing, and proof reading. Going forward, I will try writing shorter posts. Hope this is the first of many that fits that build.
I find myself talking about SDN more and more referring to myself as SDN optimist insinuating there are many pessimists out there. Why do I sense that? I’m a network guy at heart and can’t imagine the past few years without reading about the future of networking and at the same time have learned a lot in other areas of the data center and IT. It’s time to start doing. That goes for all of us. Hopefully those that are “anti” realize controllers don’t have to be all that bad and they can benefit everyone – not just the large scale networks.
Software Defined Networking is more than network virtualization in the data center. Virtual Networks can be deployed with or without programmability and/or central control. On top of that, we have these SDN principles of controller based networking, automation, programmability, overlays, and network slicing that can also be leveraged outside of the data center that very few are talking about. Look at multi-tenancy for business centers, hospitality, K-12, Higher Ed, MDUs, and even Sports Arenas. In the future, as SDN matures we’ll surely see these verticals as adopters in the Campus SDN market.
Check out my first blog @ TechTarget that goes into more detail on Campus based SDN: What makes SDN and network virtualization matter? Campus network apps
Jason Edelman, Founder of Network to Code, focused on training and services for emerging network technologies. CCIE 15394. VCDX-NV 167.
The Future of Networking and the Network Engineer