While system virtualization - and to a lesser extent, desktop virtualization - has held most of the virtualization limelight, there is also a growing trend in network virtualization.
Most of you in the network arena probably are familiar with the terms VLAN or VPN. It's a toss-up as to which is actually the older of the two most commonly used virtual network technologies, but it really comes down to whether you've been associated with remote access or traditional wired technologies.
This past fall, we were kicking around an internal discussion of what might be happening around the industry in network virtualization. At that time we really couldn't put our fingers on what vendors were doing in this particular area, and there wasn't a great deal of press associated with virtualization in networks as a whole. Sure, there was the traditional news about a new VLAN capability or a new flavor of VPN, but nothing really new and exciting to speak of.
Since that time we've hearing quite a bit of new developments. There are several interesting technologies that have emerged over the past six months to approach network virtualization issues from a variety of perspectives. With the latest system virtualization advancements, administrators can simply and easily configure a new virtual machine (VM) environment and drop it on any available platform that meets their needs.
As the functionality of that VM changes, or demands on its resources increase, the system administrator can easily transfer that VM environment from one platform to another. From the system administrator perspective that's great and the process typically takes very little time these days compared to what they used to go through to configure a new system and bring it up to an operational level.
Now, enter this scenario from the network perspective. What happens when that VM environment is transferred to a physically different platform and ends up with a completely different IP address? How is traffic going to get rerouted? Since the system administrator has the ability to schedule a VM transfer while it's operational, what's going to happen to the live, real-time end user sessions? It all depends on whether the network has been updated with the latest network armament that can rise to the occasion.
Routing of course is the biggest issue with these types of VM transfers, along with caching and load balancing. The network plumbing now has to be VM-savvy to keep up with where the systems are residing at a moments' notice. Routing tables have to be more flexible than ever, and caching elements have to be kept informed when there is a change so they can correctly redirect end user session traffic from one location to another; otherwise the sessions will become stale and the quality of the end user experience will drop dramatically.
