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.
• • 0 Comments
RES Baseline Desktop Analyzer is a free, on-line, Microsoft Windows Azure-hosted service that allows you to gain visibility into your existing desktop infrastructure through a real-time analysis of your environment and user base. RES have shown interesting innovation in the presentation of their Baseline Desktop Analyzer. The tool can work well as an initial guide on the state of your current desktop estate. But, it acts as a guide, it can present a scale of the task. To know your desktop environment fully and to know how you will need to take-on a campaign of migration you will need a wider set of information and likely additional tools and support.
In the past, virtualization architects and administrators were told the best way forward is to buy as much fast memory as they could afford as well as standardize on one set of boxes with as many CPUs as they dare use. With vRAM Pool licensing this type of open-ended RAM architecture will change as now I have to consider vRAM pools when I architect new cloud and virtual environments. So let’s look at this from existing virtual environments and then onto new virtual and cloud environments. How much a change will this be to how I architect things today, and how much of a change is there to my existing virtual environments? Is it a better decision to stay at vSphere 4? Or to switch hypervisors entirely?