I make no apologies whatsoever.
I am an unabashed fan of Vblocks: a converged IT infrastructure, produced and delivered by a converged entity (VCE), and consumed by converged IT organizations.
I was one of the earliest -- and perhaps the most vocal -- proponents of this new model. My posts on the subject drew more than a reasonable amount of criticism and outright scorn at the time.
That's to be expected, really. I was challenging conventional wisdom of how IT infrastructure should be organized and delivered.
But time has a way of helping people catch up. For many, the discussion has now evolved from "why would we do that?" to "how quickly can we get there?".
People tended to focus on deconstructing the Vblock itself, rather than the stepping back and understanding the context it was envisioned for. For example, if you run your IT infrastructure group as traditional, isolated silos, you look at something like a Vblock and say "that's not how we do things". And you'd be quite right.
However, if you've invested in delivering services vs. silos (ITaaS), the logic and appeal of a Vblock is almost irresistible.
As more IT groups are evolving their model, Vblocks continue to succeed in the market. That success enables additional investments, forming the basis of today's big VCE announcement. For me, there's two components of the announcement: the sort of thing you might expect, and a rather controversial surprise worth discussing in more detail.
So let's dive in.