CA Community






This Blog

Are you still in a "fog" over cloud computing?

Published: May 28 2010, 10:29 AM
by Robert Stroud

I've attended CA World, itSMF New Zealand, itSMF Portugal and multiple days of a COBIT 5 development workshop all in the last 10 days. The interesting thing to me was that the primary topic in all stops was the emergence of Cloud Computing!  One of the fundamental issues with Cloud Computing are the multiple definitions, so after spending some time with my friend, fellow blogger and Cloud aficionado David Wilt, I thought I would share the definition we at CA Technologies use for Cloud Computing.

Many of us, including myself have been referencing the "the Cloud" for years with references to fog, Scotch mist and even the odd cloud photos in our PowerPoints and blogs. We used to mean something amorphous, usually about networks or the Internet.  

This is not what I mean when I talk about cloud!

At CA, "cloud" means cloud computing, and it's not about a mystical, monolithic thing out there called "the Cloud." In fact, "clouds" aren't really things at all.  Cloud computing is about bringing together many existing technologies and approaches in a new way for delivering and consuming technology as services

There are indeed many different definitions out there and I believe that the best definition comes from the U.S. National Institute of Standards and Technology, or NIST.  Let me go into a little more detail for you.

When people say "the Cloud" they mean what NIST calls a public Cloud deployment model.  Public Clouds offer services to essentially anyone willing to pay for them.  These are the ones most of us are familiar with, like Salesforce.com, Microsoft Azure and Amazon EC2.

Enterprises also use a Cloud computing model to provide what NIST calls a private Cloud.  Private Clouds can be on-premise and operated by the internal IT organization using its own resources.  A managed service provider (MSP) can host and even operate a private Cloud specifically for a single customer, using the MSP's own compute resources. 

 

By: Robert Stroud
Robert Stroud serves as VP and as Service Management, Cloud Computing and Governance Evangelist at CA Technologies. Robert also serves as an International vice president of ISACA, is part of the Framework committee and was the former chair of the COBIT Steering Committee. Robert also serves on the itSMF...
Read More..

9 people have left comments:

How are you Robert ?

Thank you for your excellent and clear opinion.

Posted by: Masatoshi Kajimoto, CISA | May 29, 2010 12:21 PM

Masatoshi,

Great to hear from you - are you seeing much uptake of Cloud Computing locally?

Rob

Posted by: Robert Stroud | May 29, 2010 12:24 PM

Rob

Good to share a small amount of time with you at CA World.  I'm glad you too use the NIST definition as a starting point.  As I said in a webinar last month on the topic of Cloud Computing and its impact on service management and professional credentials, Cloud shares so many of the expected benefits of an ITSM initiative.

The importance of Cloud computing options (selective outsourcing of infrastructure) is well known to the US Federal government and the US has a law dating back to 1996 that requires IT investment decisions to have suitable and transparent practices.  These are all referenced and wrapped into NIST's definition of Cloud Computing.

A 'standard' definition exists and is used worldwide by governments and generally its based upon NIST, who is mandated to keep it relevant.  Glad to finally see a software company and fellow thought leader recognize this and help get the word out.  Thank You.

Posted by: Ian Clayton | May 29, 2010 7:54 PM

Ian,

I am sure, you, like me, have heard multiple definitions for Cloud Computing, the NIST definition provides a language we can all communicate with allowing us to solve the issue of language.

There are moves in the ISO community as well at present to define some standards for the security and governance of Cloud Computing and I am watching these develop as well.  

I do hope the industry can collectively speak the same language and remove the "Scotch Mist" or "Fog".

Regards,

Rob

Posted by: Robert Stroud | May 30, 2010 1:25 AM

Hi Rob

I am confused about the 2 groups of types of cloud that used in definitions usually.

1st the one you have used public and private cloud

2nd

Software-as-a-Service [SaaS]

Infrastructure-as-a-Service [IaaS] some also refer it as Platform-aaS

Hardware-as-a-Service [HaaS]

How does these distinctions fit in Public and Private Cloud model? Are all the above distinctions as clear as they seem eg Salesforce.com is SaaS or IaaS?

I hope I am making some sense.

Anubhav

Posted by: Anubhav | May 31, 2010 4:32 AM

Robert can you give a clear idea of cloud bursting or its simply a combination public and public cloud services.

Regards,    

Saikat                                                                                          

Posted by: Saikat Mallik | May 31, 2010 5:52 AM

@Saikat, Cloud bursting is the practice of “bursting” into a cloud when capacity has been reached in the corporate cloud/data center. The business case for cloud bursting primarily revolves around seasonal or event-based peaks of traffic that push infrastructure over its 'normal' capacity but are not consistent enough to justify the cost of investing in additional hardware that would otherwise sit idle.

Cloud bursting is a means to provide nearly immediate redirection of requests to an external cloud (Hybrid or Public or even a set of internally defined, and available "pooled" resources that are on stand by) in the event that corporate resources are depleted. When a request is received the global load balancer decides which data center (private, hybrid or public cloud) should handle the request based on its understanding of the type of capacity needed (infrastructure compute, storage etc). Other variables can of course, be introduced, but basing the decision on where to route a request on other business or technical metrics immediately moves the architecture into one of cloud balancing, not cloud bursting.

So basically there’s a rule that directs requests to CLOUD A or CLOUD B when the private CLOUD is near or at capacity. It’s a bit more complex than that in implementation, of course, but when distilled down to its basic operations, it really is that simple.

Posted by: Meghan Stabler | May 31, 2010 10:21 AM

Sailat, thanks for the comments and Meghan thanks for the detailed reply.  

In the enterprise, cloud bursting typically is the dynamic provisioning of  external resources to satisfy peak demand.  This could be enabled by “workload portability” where a virtual OS and application stack instance(s) run on internal hardware until a predefined threshold is met and then automatically supplemented with a deployment running on hosted hardware (external cloud environment).

The real challenge will be the management of the demand and the change authorization process surrounding this and of course the metrics governing the removal of the cloud capability once the demand reduces.

Posted by: Robert Stroud | June 1, 2010 3:32 PM

IT is changing! Businesses that once depended entirely on IT to deliver services are transitioning to

Posted by: CA on Service Management | June 3, 2010 10:05 AM

Leave a Comment

* An asterisk indicates a required field

* :  

:

* :  

 Submit