Follow Up on the VDC-OS Announcement

Now that I’ve gotten through the first part of discussing VMware’s VDC-OS announcement—making sure that the message and vision is a bit clearer—I can focus on some of the specifics contained within the announcement. In other words, I can talk about new features. (That should make Duncan happier.)

  • VMware Fault Tolerance (FT), formerly “Continuous Availability,” (demoed at VMworld 2007, described in my liveblog here) provides real-time VM mirroring between two different hosts. If a host fails, the mirrored VM on the secondary host picks up automatically with no disruption to the users. Marathon Technologies is working on similar functionality for Citrix XenServer, and both companies are expected to deliver next year. If VMware wants a leg up on the competition, they need to deliver this first.
  • The Distributed vSwitch enables administrators to define network settings at the cluster level, instead of on a host-by-host basis. This is huge for larger shops. Define your port group once, and you’re done.
  • As has been pointed out elsewhere, Cisco is announcing the first third-party vSwitch for VMware ESX. Alessandro points out rumors that it will run NX-OS and will be a distributed vSwitch. In any case, it will certainly bring hard-core Cisco shops closer to embracing VMware as it will give them end-to-end control over the networking environment, all the way down to the virtual port level within any given VMware ESX host.
  • vStorage Thin Provisioning will help on storage demands. I suspect this is just the use of thin provisioned VMDKs, but if anyone has any other information to share I’d love to hear it.
  • Similarly, vStorage Linked Clones just brings to VMware ESX a feature that VMware Workstation and VMware Lab Manager have had for a while.
  • VMware will finally enter the backup market with vCenter Data Recovery, which (to my understanding) will leverage VCB to provide a backup solution for the virtual infrastructure.

That’s quite an impressive list of features slated to be included in VDC-OS. What I’m also interested in seeing, though, is how the underlying components of VDC-OS—VMware ESX and VirtualCenter/vCenter—are going to change. I’ve seen rumors of 64-bit VMkernel and Console OS, and Duncan himself points out linked vCenters (which is quite cool, might I add). I suppose that will be part of the “Tech Preview” sessions that are going on later this week.

OK, that’s it for now; need to run off for another session. Stay tuned here and on Twitter for more information!

Tags: , , , , , , , ,

thanks scott! what an amazing VMworld, already…

Great summary Scott! I wish I was there, but you ease the pain somewhat. :)

The whole Nexus discussion has been quite a distraction from the main elements discussed today at the show (esp. since Cisco wasn’t mentioned directly in any of the Tech. Exchange/Partner sessions I went to — even ones focused specifically on I/O virt. and distributed virtual networking.) We all know who they meant, but…

Cross-posting from a comment I left on a French blog that intimated that DVN/DVS were Cisco’s doings:

Just to be clear, DVN and DVS aren’t Cisco’s technologies or creations, they are larger branding associated with VMware’s new “v-everything” marketing efforts that are grouped under the vNetwork moniker.

DVN/DVS speak to the vNetwork elements and their various application to allow functional interface with the vkernel via API (at both the network and appliance level — which includes what we used to know as VMsafe.)

Great summary, Scott. For me, the security implications continue to mount — with lockstep, record/replay, F/T, and the underlying chipset enhancements coupled with IOV — holy crap!

..then we’ve got “cloud federation” ;)

/Hoff