The Virtualization Practice

Tag Archive for Licensing

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.

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.

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.

Licensing:  Pools and Architecture Changes?

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?

Microsoft is making changes to its licensing policies to provide enterprise customers with a fast track to the cloud. The changes dubbed “License Mobility” announced at the Microsoft Hosting Summit in March this year,will move will allow customers with Software Assurance to move their applications to a cloud services provider without paying a premium for the added flexibility this will bring.

VMware View users along with Citirix XenDesktop and Quest vWorkspace have an iPad client for their respective solutions. Personal device use may seem appealing in reducing the demands on IT support – but to fully comply with the license agreements can incur additional license charges, and those charges are difficult to manage. Despite the advertising blurb attached to the free clients, the headaches for finance and IT are not over yet.

Managing licensing and utilization costs is a mess today in the physical world. Introducing elastic scaling of workloads into a hybrid private/public cloud introduces new uncertainties and new software licensing metering and compliance issues. This is particularly true in the case of enterprise applications which are licensed by the enterprise from the software vendor and then deployed on an as needed basis on Iaas or PaaS clouds.

A change to the Microsoft Client Access License (CAL) bundle is a rare event – the last time it happened was about 10 years ago; so any change to the CAL bundle has to be seen as a significant indicator of Microsoft’s core values. Or so you would think. Assuming that is right, last week’s announcement at the Microsoft Management Summit of changes to the Core and Enterprise CAL bundles need careful analysis. Changes to the CAL are a strategic driver towards new product adoption and represents a clear indication of Microsoft’s long-term goals and aspirations. With that in mind we can infer from this latest change how Microsoft views desktop virtualization.