VM Stall: How to Avoid A Sneaky Virtualization Project Enemy

CIO — Virtualizing and consolidating data-center servers provides such clear a financial benefit that there are few companies of any size, in any industry that shouldn't virtualize at least some of their servers and applications, industry analysts say. But companies that start virtualization projects looking for cost savings, without planning for a second phase of migration that requires spending more on new tools than the project might save in short-term costs, will get stuck in phase one — saving money on hardware, but getting only a fraction of the benefit of the virtualization products they've bought, analysts add.

The cost benefit of getting as many as 10 or 20 virtual servers for the price of one physical box drove many companies to migrations that covered as much as 25 percent to 35 percent of all the servers targeted for conversion, before hitting "VM stall," a virtual halt in migrations caused by the most subtle cost- and organizational issues that affect virtualization projects directly, according to James Staten, principal analyst at Forrester research (FORR). "Companies can get close to the 50 percent point [in a P2V migration] still using the same thinking they did in the physical world," Staten says. "Obvious costs like licenses, how many machines you can take out of an environment, how many VMs you can put on a host all make one cost picture. Beyond that you get into issues about performance and capacity management, and the amount of effort needed for support — a lot of companies don't take those fully into account."

Planning to virtualize every workload on every server without modifying the way IT plans capacity requirements or the way it allocates computing resources and IT staff support time, leaves IT departments with a lot of duplicated processes — and a steadily dropping return on investment as a P2V migration expands, says Chris Wolf, research VP at Gartner.

"Trying to replicate the same structures you had been using, with virtual servers, gets into a cycle of diminishing returns pretty quickly," Wolf says. Keeping virtualization projects on track requires changes in both organization and technology — and the need to keep the two coordinated according to the particular stage of migration, Staten says. Here's some advice for avoiding stalls during four key phases of a virtualization project.

Phase 1: Technical efficiency and consolidation

The first, ecstatic wave of virtualization saves far more money, far more quickly than at any other time during the migration to or operation of a virtual infrastructure, according to Gary Chen, research analyst at IDC.

The cost benefit of eliminating 10 physical servers and replacing it with one larger, more automated box often gives both IT and business-unit managers a false sense of success and unrealistic expectations for the future, he says.

Many IT groups stick with the same set of cost metrics to estimate success, which usually means focusing only on how densely virtual machines can be packed into physical hosts, not investing in management tools or training that give IT managers a better idea of how to allocate virtualized resources in new ways, Chen says.

"People have to move their thinking away from something a lot of them are proud of — their physical server-to-virtual server ratio, or how many machines they can take out of an environment," Staten says. "That's an interesting thing to brag about, but completely irrelevant. The real need is to shift to the point that you can deliver greater efficiency — higher sustained utilization and peak utilization of their whole pool of computing resources."

Phase 2: Picking targets, simplifying administration

The next phase of a migration  and its cost-justification  requires more specific knowledge of what individual VMs are doing, for what business unit, and what resources they require, Staten says.

That requires more than high VM density to keep the ROI positive; it requires changes in IT administration and support to improve processes like change management, provisioning and incident management that don't work effectively within older organizational silos, Staten says. Without the ability to build resource-inventory lists that are more detailed than just the number of physical servers available, IT managers can't intelligently distribute particular VMs or workloads across the available servers, let alone to other data centers in companies that have very far-reaching virtualized infrastructures, Wolf says.

"You start to look at all the resources — CPU, memory, storage — as a pool you can allocate," he says. "You can't do that without visibility into all the resources or within existing management silos."

Getting to the point of even automating the provisioning of VMs and putting limits on their resource use, mobility and lifespan requires new management tools that are often limited in scope to just one vendor's software, Staten says.

Getting beyond the first big opportunity for VM stall — the reorganization of administration and allocation of computing resources  means giving sysadmins responsibility for a set of VMs according to the business unit that uses the VMs, or the pertinent applications or other factors, not the physical location of the servers.

Failure to allocate human resources efficiently causes efforts to be duplicated, extra work and gaps in responsibility, all adding up to a huge waste of resources when VMs are floating around without anyone clearly responsible for them.

"Sprawl is the typical problem there for companies that are not doing lifecycle management or automating any of the procedures involved in systems administration or support," Staten says. "That's where the change in thinking needs to happen or progress typically starts to slow down." At the most basic level, it's necessary to know what all those virtual machines are doing, or whether they're doing anything at all.

Data-center administrators consistently report that about 15 percent of the servers they maintain aren't doing anything useful. That is, they're running and being properly maintained, but are not being used by any end users or applications in an average month, according to Sumir Karayi, CEO of 1E software, a U.K.-based asset-management vendor that sponsors regular studies of resource-utilization efficiency in data centers.

"IT is typically asked only for uptime; their job is to keep things running, not ask why it's running, so they look at utilization of resources, not workloads." Karayi says. "If a server is being backed up, patched, rebooted to install patches, it can look quite busy just doing housekeeping work even when no one is using them. With virtual servers it's even easier because there's not as much of a perceived cost to running them without doing any real work."

Continue Reading