Failing to live up to cost-saving expectations is one of the major points of dissatisfaction with cloud and virtual computing among both IT and business-unit managers, according to a report released by Symantec this week.
The inability to define costs, benefit and usage levels in enough detail to create realistic expectations is one big reason for the disparity between what virtualization buyers expect and what they get, according to John McGee, VP of product marketing for Symantec, who is responsible for the report.
Besides buying better reporting and analysis tools, the VMware division that used to be the Springsource Java dev tool company loosened up licensing for the newest version of its vFabric application development and deployment platform.
Rather than having to pay license fees for a set number of CPUs – set manually when the application is deployed – buyers of the new vFabric 5 allows customers to pay for licenses according to the number of VMs in which it is launched.
That's a far more accurate way to measure actual use than the previous method, which was based on a physical resource the apps don't use consistently, according to David McJannet, director of product marketing for VMware applications.
"When you have an application deployed across pools of infrastructure, it will be spread across virtual machines on 16 CPUs at some times of day, and on only 10 at other times," he said. "That is a very complex way to license applications when the resources they use shrink and grow over time, so we think the virtual-machine-based approach to licensing makes more sense."
It allows apps written for internal VM infrastructures run and be accounted for according to the resources they use – just as SAAS or cloud-based apps are designed to be.
Current vFabric customers can switch existing licenses from per-CPU to per-VM, mix the two methods, or switch from one to the other with relative freedom, McJannet said.
vFabric 5 has other additions, too: Better integration with VMware's vSphere virtualization servers that allow Java and vSphere more power to negotiate memory use according to demand of the applications, which conserves RAM on the physical machines and reduces the total amount of hardware required, McJannet said.
vFabric 5 also got more support for mobile devices to let apps built for vFabric run or display on any device that supports a browser.
"We're trying to create more efficiencies to developing apps for vFabric, to eliminate sand in the gears of more development," he said.