Commentary

Charles Babcock
InformationWeek  

Virtualization Is IT Journey That Begins With Consolidation

As IT shops look at their gains from consolidating servers, they realize this was just a first step brought about by implementing virtualization. Once you've consolidated, you realize how many more steps are both possible and necessary if virtualization is going to lead to more payback.

As IT shops look at their gains from consolidating servers, they realize this was just a first step brought about by implementing virtualization. Once you've consolidated, you realize how many more steps are both possible and necessary if virtualization is going to lead to more payback.In this week's PDF issue, I had the chance to take a look at how four users of virtualization in productions systems had gone about the task and counted their savings.

Afterward, in a conversation with Steve Herrod, CTO of VMware, I realized they are not unique and may be simply examples of a very broad trend. The Roswell Park Institute for Cancer Research, Rooms to Go, Orchard Supply Hardware and the Owen Bird Law Corp. are all examples of firms that began with server consolidation and have started to move beyond that into network and storage virtualization to realize greater gains.


More Storage Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

"We see customers going through different phases. We keep using this term,' the journey,'" said Herrod. Virtualization allows IT to be separated into its logical parts instead of being driven by physical installations and hard wired connections. In a fully virtualized data center, storage can be treated as a logical resource, re-organized around the principle that it exists for the benefit of a large group of servers. "For the whole of IT itself, it's a pretty dramatic change. IT is challenged to become more like a service provider," said Herrod.

If you can define services in advance of demand, as virtualization allows, then you can set up those services in advance and speed the delivery of IT services. You can even move to more of a self-service environment with your customers. This is easy to state, harder to do. Access must be controlled. Users must be defined not only with a unique identifier but with a role that might vary under different circumstances. Nevertheless, identification must always be tied to the appropriate role and correct level of access to data and resources.

If the roles and policies governing them can be set up in advance, then IT needs to intervene only when the policies are being violated or a user claims an exception to the rules must be created.

A conclusion hidden in the steps toward virtualization is that "consumption of IT is being separated from production," Herrod says.

The manufacture of services can be done in advance. After virtual servers and appropriate networking and storage are created as logical units, then the consumption of these services needs to be monitored and charged for on a pay-for-what-you use basis.

Departments may be shocked at what they find they are consuming of the common resource. Herrod quips that future tracking of use and chargeback will lead to "the seven stages of grief when they see the bill, starting with denial." It didn't matter to them they still had 15 Windows Servers they were no longer using. There was no direct cost accounting, so in the past they just said "no" when asked by IT if they could be shut down. "The cost of what they were using was hidden in the annals of the IT budget," he notes.

Nevertheless, this separation of production from consumption "is the key to fast-moving IT," said Herrod. Virtualization is the key to much more than the savings of server consolidation. The implementers that we cite this week in the cover story of our downloadable PDF issue, Virtualization Beyond Consolidation, are discovering this for themselves and sharing the results.


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