Reuven Cohen's "ElasticVapor" Blog

So it would seem my cloud standardization post has hit a nerve with a few. So I would like to post a some follow on ideas I've had, since writing it.

First of all I'm also not totally sold on the whether or not cloud computing is ready for a cloud standard just yet. What I do think we need is a reference implementation (Platform & Infrastructure) and common extensible API - "CloudVirt"

This API may someday form the basis for a standard, but in the meantime gives us a uniform API to work against, so whether you're using Google App Engine or Force.com, GoGrid or EC2, Nirvanix or S3, you'll have a central point of programmatic contact. I personally don't want to have to rewrite my platform for every new cloud provider's API, which is exactly what we're doing now.

Also a few people have point out the CIM (Common Information Model) could be a ideal starting point for a cloud API, for those who are unfamiliar, CIM is an open standard that defines how managed elements in an IT environment are represented as a common set of objects and relationships between them. This is intended to allow consistent management of these managed elements, independent of their manufacturer or provider.

For those interested in joining the discussion, please signup for our cloud computing group.

• Creating a Common Cloud Computing Reference API - Part One
• Cloud Computing - The User-Friendly Version of Grid Computing
• Virtualization & Cloud Computing: Perfect Together
• Marketing the Cloud Computing Paradigm Shift
• Merrill Lynch Estimates "Cloud Computing" To Be $100 Billion Market
• IBM Leads 13 European Partners in Cloud Computing Initiative
• A Brief History of Cloud Computing: Is the Cloud There Yet?
• Cloud Computing vs. Elastic Cloud: What's the Difference?
• Twenty-One Experts Define Cloud Computing
• Enomaly Founder & Chief Technologist to Present at SYS-CON's Cloud Computing Expo
• Cloud Computing Journal: Current Themes & Topics
• Is Microsoft Starting a Cloud Computing Price War?