Commentary

Charles Babcock
InformationWeek  

Virtual Lab Managers Pave Path To Cloud

I've tried to make this point before: The path to the cloud lies through the virtualization of your own data center infrastructure. The two things are intertwined. And just when I'm wondering how to get the point across again, along comes a "snapshot" from Voke Research to clinch the case.

I've tried to make this point before: The path to the cloud lies through the virtualization of your own data center infrastructure. The two things are intertwined. And just when I'm wondering how to get the point across again, along comes a "snapshot" from Voke Research to clinch the case.Theresa Lanowitz, founder of voke Inc., a market researcher, and voke analyst Lisa Dronzek made a snapshot of 100 users of virtual lab management software between August and February through phone and online interviews and came up with some specifics that flow from adoption of virtual lab management applications. In addition, they found that the benefits of consolidating servers under hypervisors is well known, but "virtual lab management technology and its benefits are less visible and less public." That's because selling a hypervisor and its operating environment is clearly in the sphere that VMware, Citrix Systems and Microsoft care about; virtual lab management, not as much so. While the primary vendors have their own offerings, first in the lab management field were third parties, such as Surgient, founded in 2003; Akimbi, acquired by VMware in 2006; and Skytap, founded in 2006. VMLogix wasn't far behind, launching VMLgix LabManager in July 2007.

But adopting lab management software is a change that has far reaching implications. It's the system that lets you set up a virtual machine provisioning system, determine what types of virtual machines are to be created, then allows end users to commission them themselves. Usually a charge-back system is included. The software gets its name from a primary user, the software development team that needs a lab of servers on which to test their new system.


More Storage Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

But as the foregoing functions indicate, once you've got lab management installed, the potential end users may extend far beyond the development team. And once you're practiced at setting up virtual machines and allowing end users to activate them, you're well on your way to cloud computing. The cloud, after all, is as much about end user enabling as it is new technology, something some of its most dense critics cannot grasp.

Some specifics of what they found:

In terms of physical servers, 23% of lab management software users eliminated 1-9 machines; 31% eliminated 10-19 physical machines; another 31% eliminated 20-150 machines; 15% eliminated 151-500 machines. The average implementer eliminated an average 101 physical servers.

Lab management software reduces the total software servers, for reasons that weren't spelled out in the March 22 report. More than one software server often resides on one physical machine. If the lab manager for the development team doesn't need to keep one copy of every environment running, then the total number of servers, both physical and software, can be reduced. Virtualization allows that by storing a server not needed with the current project and activating it again off of disk, when it's needed. Of those surveyed, 34% said they reduced servers by 1-9 units; 33% said they eliminated 10-19 servers; 25% said 20-150 servers; and 8% said 151-500 servers. The average implementer eliminated 57 servers.

The resulting return on investment was dramatic: 27% said they saved between $100,000 and $199,000; 37% saved between $200,000 and $499,000; 18% saved $500,000 to $999,000; 9% saved $1 million to $6 million; and another 9% saved more than $6 million.

The value is obtained by "the reduction of physical environments, immediate access to needed environments through rapid provisioning, the reduction of tactical work (such as procuring and assembling a physical server), and the increase in important strategic work…" the report said.

"The technology is strategic, empowering and not difficult to adopt and implement," the report concludes. And I would add, it positions the organization to make a transformation, when it is ready to, to execute part of its operations in the on-premises data center and part in the external, public cloud.

An executive summary of the report is available on the vokeInc. site.



Data centers have never been more strategic. But growing demands, flat budgets, and emerging technologies have IT teams sweating. That story and more in our March 22 all-digital issue. Download it now. (Registration required.)


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links