Every now and again, we like to use this forum to provide commentary and context on happenings in the industry. Today’s news from Waltham, Mass. and Palo Alto, Calif. is a good example. On the one hand, there’s a Microsoft competitor. On the other hand, there’s a Microsoft partner (see today’s joint webcast). And if there’s such a thing as a third hand, there are implications for Red Hat, perhaps even IBM.
So what’s our take?
First, the Microsoft and Novell alliance has been very successful. It’s been 3.5 years since the big announcement with Novell, and we have more than 475 customers who’ve chosen to work with Microsoft and Novell. We’ll continue to work with Novell around technical support and interoperability. The joint interoperability lab in Cambridge is very active, and we recently announced work together in high-performance computing. Oh, and did I mention today’s joint webcast on heterogeneous datacenter 😉
Second, the vFolks in Palo Alto are further isolating themselves within the industry. Microsoft’s interop efforts have provided more choice and flexibility for customers, including our work with Novell. We’re seeing VMWare go down an alternate path. As one of many examples of our work with open source communities, we’re adding functionality to the Linux Integration Services for Hyper-V. In fact, we have an RC version of the Linux Integration Services, which support Linux virtual machines with up to 4 virtual CPUs. In fact, we’ll talk more of this on June 25 at Red Hat Summit. For more meat, see Matthew’s post about what you need to know about Linux on Hyper-V. And if you’re talking about technical support, let’s not forget the Server Virtualization Validation Program, which includes Red Hat, VMWare, Novell, Cisco and others.
Third, looks like VMWare finally determined that virtualization is a server OS feature. I’m sure we’ve said that once or twice over the years ;-). The vFolks now plan to ship a full version of a server OS with vSphere, and support it, to fulfill their application development and application deployment plans.
Fourth, this is a bad deal for customers as they’re getting locked into an inflexible offer. Check out the terms and conditions. For example: “Customers may run SLES with the accompanying patches and updates subscription entitled by a VMware purchase only in virtual machines running on VMWare vSphere 4.0 and 4.1 hosts that have active vSphere SnS with VMware.” So be sure not to drop support or you’ll invalidate your license. Or maybe just stick with small deployments.
Last, the vFolks have no public cloud offering, like Windows Azure, like Amazon EC2. While we’re demoing and building capabilities so customers have a common and flexible application and management model across on-premises and cloud computing, they’re stitching together virtual appliances to fill the void. Don’t forget – the next version of System Center Virtual Machine Manager will configure VMs from VMWare and Citrix.
What are your thoughts?
Patrick O’Rourke, director of communications, Server and Tools Business