As the virtualization ecosystem continues to grow and mature, the focus is settling less on the aspect of the hypervisor...
and more on critical aspects that have fallen outside of the traditional server virtualization platform.
Development support has continued to be a greater focus with Docker and other container technologies leading this next generation of application development. Automation has become another focal point affecting all aspects of the virtualized data center. Being able to deploy virtual machines (VMs) faster and more efficiently is becoming a business requirement. While VMware is working on both of these efforts, one of its true focuses has been on network virtualization. VMworld put a lot of focus on not only what its NSX software can do but how it integrates with other products. While this may seem like more marketing than anything else, it is, in fact, something a lot bigger.
When VMware first unveiled NSX, the biggest buzz centered on why Cisco was not one of the supported vendors. Few people knew what it was or why it was even needed. Traditional networking still worked and scaled up to support virtualization very well. VMware made a $1.2 billion gamble on software-defined networking. NSX has faced lot of questions and generated plenty of interest, but there haven't been many well-understood use cases. However, this has not stopped VMware from integrating NSX with products such as vCloud Suite, and vRealize. With this level of integration, you have to wonder if you can still use VMware products without NSX software. I have some good news and bad news for you.
Yes, it's still possible to run VMware virtualization without NSX -- in fact, you don't even need distributed switches. Many shops are familiar with the basic networking available with standard switches. And, if what they're used to is working, why fix it?
That line of thinking has led to the buzz about the hypervisor becoming a commodity and the idea that the hypervisor vendor doesn't matter. If your IT efforts and data center are going to stop at the virtualization layer, then, yes, the hypervisor really is a commodity. However, when you take that next step into the much larger ecosystem, your hypervisor vendor does matter. No matter which hypervisor you choose, it needs to do more than simply allow VMs to communicate. While VM communication was initially simple and required little more than standard switching with basic software control, today's security needs require more. It's not a question of if you will be attacked, but when.
The traditional data center model simply does not work with the security needs of today's world. When VMware announced the software-defined data center, many were unsure what it was or where security fit in. The same was initially true of NSX. After all, unless you were a larger hosting provider, the benefits didn't seem to outweigh the cost. It was not until VMware announced micro-segmentation of the network that the lights turned on, and NSX gained wider attention from all types and sizes of business. Having the ability to implement security policies down to the virtual network interface card level has helped to change the data center from a perimeter security model to a model where security can exist at every node in the network. This has the potential to become a hacker's worst nightmare, where security is no longer layered but omnipresent.
While few of us like to embrace security and the "inconveniences" that go along with it, traditional security is no longer enough. Security breaches have become too frequent and the damage they cause is far outpacing our imagined worst-case scenarios. VMware is taking us down a path not of multilayer security but of "micro-security," where an attacker cannot turn a corner without running into another security barrier.
While this has been tried and unsuccessful before, VMware has come to the table with an approach that balances performance, management and cost. By incorporating NSX software into the core of VMware products, we are running out of excuses not to use it.
In a modern car, the seat belt alarm sounds reminding us to buckle up; and while most agree that seat belts make us safer, many of us wouldn't use them if not for the audible nagging. We are creatures of habit that need the additional push to ensure we are keeping ourselves protected. VMware integrating NSX software and the security into its core products brings this safety reminder into our virtual world. While VMware doesn't require us to use NSX, our businesses should require it. VMware just happened to see that a few years before we did.
Answering common VMware NSX software questions
VMware NSX roadmap focuses on security
VMware adds NSX certification options
Requirements to run Cisco ACI and VMware NSX
Hardware and software requirements for VMware NSX