I’ve just posted some guidance for developing a Cloud Computing Roadmap on my Strategic IT Architecture Web site. Obviously, it’s a complex topic and there are many, many variations on the routes you might map out.

One approach that I didn’t mention in that post – space is limited in a blog posting – was an approach that mitigates and contains risk, while still delivering a solid foundation for internal Clouds and near-term ROI and operational benefits.  Server platform virtualization.

Virtualization is a mature and proven platform architecture that greatly improves asset utilization and can significantly enhance operational efficiency. Clouds are based on a virtualized platform.

In order to fully evolve into a Cloud, and provide all of the benefits that Clouds offer, you will eventually need to enhance the virtual environment with some additional capabilities – e.g., self provisioning, dynamic resource allocation, measured/metered usage. You’ll also want to make some enhancements to the platform architecture to better accommodate multi-tenancy, elasticity and other powerful Cloud capabilities.

But as a solid first step toward a Cloud Computing target, and as a means of containing risk – including the risk of moving core applications to an external, still unproven commercial Cloud – consider implementing a virtualized computing IT ecosystem.

One additional technical point: As you develop your implementation plan for a virtualized platform, you do need to consider what kind of “Hypervisor” you’ll use. The most critical decision is whether to use a Type 1 (bare metal) product or a Type 2 (hosted) Hypervisor.  Type 1 provides maximum performance because it executes on the hardware (bare metal) and provides its own operating system support. Type 2 is installed as a guest operating system on a hosted system, so it sacrifices some performance because it’s running in a layer above the native OS.

Here’s a quote from a briefing that one of my clients used to kick off their Cloud strategy discussions. The definition is valid, but only for one specific model of Cloud Computing – public (commercial) clouds.

“Cloud computing refers to the practice of purchasing computer services that are stored and maintained by a third-party contractor, instead of housing all the equipment and software on-site.”

When this slide appeared on the screen, 10 minutes into the kickoff session, most of the leadership team reacted immediately. Their response, based on the misperception created by that focused and incomplete definition, was… we do not, and will not outsource our IT platforms to anyone!

It took a quickly improvised white-board session to clarify the opportunity and to get this initial strategy session back on track. There are tremendous benefits available from the use of an appropriate Cloud Computing model and its enabling technologies.

Examples of the strategically significant Cloud models are:

• Public Clouds (defined above) – examples include Google (e.g., GAE), Amazon (e.g., EC2, S3), and Microsoft Azure.
• Private Clouds – managed for the use and benefit of a single organization. Significant benefits from consolidation and virtualization of platforms and operations.
• Community Clouds – shared by multiple communities of interest. Benefits from pooling resources and operational costs.
• Hybrid Clouds – Consisting of Private Cloud(s) and augmented by integration with Public Clouds for “cloud bursting”, auxiliary data storage, or for access to commercial applications.

One common example where lack of specificity in the definition of the Cloud results in a misleading conclusion, the recurring argument that security is a major inhibitor to adopting Cloud Computing. This concern is only valid (to some degree) when referring to commercial Cloud vendors who have not, yet, reached security compliance. Growing maturity in this space and lessons learned have shown that multiple data centers, consolidated into a Private Cloud can be hardened, secured and managed to a much higher level and at lower cost than is possible across multiple data centers.

Bottom line: the potential benefits are significant. Just follow well-proven best practices – understand the problem space, clearly define goals, identify the risks, assess benefits (ROI being only one measure), identify the best, most appropriate solution (e.g., what’s the best Cloud model) – and you can craft an effective roadmap to reach your target. Significant benefits await!

If you’re interested, I’m discussing a more detailed approach to developing a Cloud Computing Roadmap on my Strategic Architecture blog at http://StrategicITArchitecture.com.

It looks to me like we are very close to the peak of the Hype Cycle – lots of, often irrational, press; “silver bullet” claims; rush to adoption without attention to basic best practice (which will result in early failures that deepen the Trough of Disillusionment!).

Note: I’m referring here to enterprise cloud computing – private, community, and hybrid — not the simple SaaS offerings, like productivity tools. Generally, those are pretty low-risk with minimal impact/risk.

One of my concerns is the lack of clarity in definition, and overloading the use of the term, Cloud Computing. I do believe that we’ve established the foundation for clarity in understanding what Cloud Computing means and the options for leveraging the opportunities it offers (for more information, see http://www.StrategicITArchitecture.com). But it looks to me as if the momentum (frenzy?) has built to the point that many prospective adopters are not paying attention to basics and are rushing to judgment.

Clouds (in their various flavors) represent a powerful and positive evolution in our delivery and consumption of IT resources and services. Ensuring success in choice of strategy, reduction of risk, and the earliest possible ROI can benefit from tracking the Hype Cycle and factoring it into the decision making process. Prudent adoption strategies will ensure that we reach the Plateau of Productivity.