Important facts about vSphere 5's new pricing model

VMware is charging based on a pool of memory in virtualized servers that can be shared as well as on the number of CPU cores.

By David Davis, Computerworld |  Virtualization, VMware

The newly announced VMware vSphere 5 has a new "pooled" pricing model that charges customers based on the virtual memory configured in a virtual server. The model does away with limitations on the amount of RAM and number of cores, and it is the only way to buy the new vSphere version.

Announced on Tuesday, July 12 at the VMware Cloud Infrastructure event in San Francisco, vSphere 5 also sports numerous new features including storage distributed resource scheduler (SDRS), auto-deploy, a Linux-based virtual appliance option for vCenter and a Web-based vSphere client.

All of these features are beneficial and powerful (full disclosure: I was a beta-tester of vSphere 5), but of particular interest to many customers are the pricing changes because of the potential financial or administrative impact.

What is vRAM pooled pricing?

The per-virtual-machine (VM) pricing model has become standard for VMware products including vCenter Operations and vCloud Director. But some VMware shops don't like this pricing system, because it uses a flat price across all VMs, no matter the size of the VM -- and of course not all VMs are created equal. There was some speculation that the next version of vSphere would also be based on this model. Instead, VMware has added an entirely new variable to its pricing lineup, one that I don't believe has previously been used for software licensing.

VMware resources

Where to learn more about the pricing changes and how they might affect you:

VMware's vSphere 5 white paper (PDF)

A VMware blog entry that explains more about the vendor's thinking behind the pricing changes and how it works

VMware's video explaining the pricing changes

With vSphere 4, for each socket license you purchased, there were restrictions on the number of CPU cores per CPU socket (6 cores for the Enterprise, Essentials and Essentials Plus versions of vSphere 4, and 12 cores for Advanced and Enterprise Plus). There was also a physical RAM limitation per host (256GB for Standard, Advanced, Enterprise, Essentials and Essentials Plus, and unlimited for Enterprise Plus).

This setup didn't work for some customers or for VMware. Sometimes customers would hit the core limits and couldn't easily grow their infrastructure.


Originally published on Computerworld |  Click here to read the original story.
Join us:
Facebook

Twitter

Pinterest

Tumblr

LinkedIn

Google+

Answers - Powered by ITworld

ITworld Answers helps you solve problems and share expertise. Ask a question or take a crack at answering the new questions below.

Join us:
Facebook

Twitter

Pinterest

Tumblr

LinkedIn

Google+

Ask a Question
randomness