Cloud CIO: 5 Key Pieces of Rollout Advice

Once you decide to take cloud as the medicine for what ails your IT organization, you'll have to change organizational process, not just infrastructure says CIO.com's Bernard Golden. He shares some expert advice on that, plus standardization, training, and related rollout issues.

The spread of enthusiasm for cloud computing seems unstoppable. Cloud computing — a term that was unknown prior to 2007 — has been named by Gartner as the number one priority for CIOs in 2011. One cannot recall a technology development that has gone from unheard-of to a key role in IT plans so quickly. So why has this unprecedented fervent cloud furor come to pass?

Cloud Costs: CIOs Need to Plan Better

The Cloud CIO: A Tale of Two IT Futures

One way to approach understanding this phenomenon is to mimic the medical process, in which examination of the patient's condition is first performed, followed by diagnosis, and then treatment via prescription.

The examination of facts is undeniable. Every IT organization extant suffers from the following complaints: Endless waits for provisioning, capital invested and then used at less than 10% of capacity, and inability to cope with the growth brought about by cascades of new data, attachment of new devices, and creation of new applications designed to enable collaboration within and between organizations. Clearly a malady is overwhelming business-as-usual IT.

Turning to diagnosis, it's obvious that current operational and organizational models were developed for a much smaller scale, in which the cost and low productivity of manual provisioning were acceptable, in part because there were no alternatives. Today, however, lack of automation now threatens the ability of established IT organizations to survive.

Consequently, the prescription most often proffered to IT organizations is cloud computing, which, overlaying the existing physical infrastructure with an automation software framework, appears to be just what the doctor ordered. And, indeed, CIOs are now eagerly reaching for this medicine, though they are perhaps unsure if the vendor is offering a magic potion or a harmful nostrum.

The remedy most often selected is a private cloud computing infrastructure, despite the potential side effects present (as I wrote about last week).

But what happens after you swallow the pill? In other words, once you've committed to cloud computing and have an environment available, what do you do? Turning away from our extended medical metaphor, here are some action steps to take:

1. Standardize your offerings. Part of the inefficiency and high cost of the current mode of operating IT is the "have it your way" responsiveness of most IT organizations. Customization is the enemy of automation and efficiency, so reduce it.

Create a standard set of pre-allocated virtual machines that a developer can choose among. A service catalog approach is exactly right here. We recommend mirroring Amazon's configurations: small, large, extra large, etc., with the same amounts of memory and storage. (Apparently, Cisco agrees with this recommendation, as it announced its intention to acquire newScale, a service catalog provider often used to manage standard catalogs of cloud offerings within corporations).

2. Create pre-packaged software stacks. In addition to standardized virtual machine configurations, enriching those configurations with pre-packaged software stacks offers several benefits. First, it moves the organization toward additional standardization. When a developer can get started more quickly rather than having to spend time installing and configuring software components, he or she is more likely to develop solutions aligned with approved software stacks.

Second, offering pre-configured software stacks reduces errors from misconfiguration, always a good thing. Third, and by far the most important, it raises developer productivity. It can't be stressed enough, offering self-service virtual machines and storage is only table stakes. The pace of innovation Amazon is providing to ease developer use of AWS is amazing, and providing raw compute capability in the face of higher productivity alternatives is a recipe for being ignored. Amazon is quickly assembling a PaaS set of components, so don't believe your basic cloud computing will be sufficient going forward. Start evaluating how to extend your infrastructure to provide even higher developer productivity.

1 2 Page
Join the discussion
Be the first to comment on this article. Our Commenting Policies