VMware has updated the vRAM pricing for vSphere 5 to address certain customer issues, and deserves a great deal of credit for acting this quickly and decisively to the feedback that was generated by the initial announcement. However, even with the new vSphere 5 vRAM pricing the question is now raised as to whether competing and less expensive virtualization platforms are acceptable for some entire companies, and some use cases within what used to be 100% VMware shops. VMware has created an opening for Microsoft, Citrix, and Red Hat. As this sorts itself out, the virtualization platform landscape will change – resulting in a minimum in a new focus on tools to manage multiple virtualization platforms.
VMware has made significant changes to the recently announced vRAM based pricing. The single most significant change is that potential barriers to the virtualization of memory intensive business critical applications have been eliminated by ensuring that no application no matter how big can cause a charge of more than 96GB to be levied against the pool of available vRAM.
I was reading through a recent article about the new Java 7 release, which contradicts Oracle’s current support statement with respect to licensing. The License from Oracle exclusively states Java 7 is only supported on those hypervisors Oracle currently supports: Oracle VM, VirtualBox, Solaris Containers, and Solaris LDOMs except where noted. That last phrase is rather tricky, so where do we find such notes. Is the noted the support document stating that they support Oracle products within a VMware VM? Or is it somewhere else in the license? This leaves out all major hypervisors: Citrix, VMware, and Microsoft. If you cannot find a note saying things are supported, somewhere.
This implies quite a bit for the future of Java support within most PaaS environments being built today. In essence, they cannot upgrade to Java 7. Which means they may fall behind. This would impact OpenShift, Amazon, Google, CloudFoundry, SalesForce, and others.
VMware has done the right thing by taking care of their enterprise customers and making sure that they know that they can purchase vSphere 5 licenses under the terms of their existing ELA’s. The vast majority of smaller customers who run a small number of purchased applications are unlikely to be impacted by the new vRAM licensing, as their is probably plenty of vRAM headroom to take care of their needs. The issue is with customers who are not quite large enough to have an ELA, and who have sophisticated mixes of purchased and internally developed applications – and who are trying to push the density envelope in order to maximize their return from their investment in VMware. This customers are going to have to look at the new licensing in the above terms and make their own decisions.
Five months since Goldman Sachs took a reported 28% stake in UK desktop virtualization specialist AppSense, the signs are that it is starting to expand its US presence by hiring a new Silicon Valley design team that will be based in the company’s Santa Clara offices.
The 7/7 Virtualization Security Podcast with Steve Kaplan, Vice President of INX’s Data Center Virtualization Practice and well known ROI/TCO expert within the virtualization and cloud space, joined us to talk about the ROI and TCO of virtualization and cloud security. We discussed someways to view virtualization and cloud security, but mostly the fact that many people may not think ROI or TCO even applies until a problem occurs and you need to rush in and find and fix the leak that lead to a break-in. In essence, the ROI of proper security tools is your entire business.
VMware is already the most important, and with vSphere the best systems software vendor on the planet. This is true not only based upon the current success of the vSphere platform, but the quality of the long term strategies in place for vFabric, vCloud, and vCenter. With vSphere 5, VMware can ill afford distractions that detract from the momentum of the attack upon the remaining 60% that is not virtualized. The strategic investments in vFabric, vCloud, and vCenter then call into question of viability of having a desktop virtualization business (View) that is today in product and tomorrow in vision a minor subset of what Citrix is delivering and articulating.
As mentioned in a couple of recent posts, I have been building a prototype application using Open Source technologies that I plan to install on a number of available PaaS cloud platforms. The application is written in Groovy (with some bits in Java) and built on the Grails framework. This article is about my use of RedHat OpenShift PaaS and the controls available.
Business Agility ...
• • 2 Comments
The single most dangerous part of this new pricing (to VMware) is rooted in the following fact. What is left to virtualize is very different from what has been virtualized to date. If what VMware has done is change its licensing around to replace one metric (cores) with another (vRAM) in a manner that would have allowed it to get the same revenue from its existing customers to date, then VMware has totally missed the boat.