So my friend Troy starts this great discussion: ITIL Castles In the Cloud. With song! Read on:
Rhetorical Question: But wait I thought that cloud computing strategies are meant to simplify IT service provisioning? I cut the supplier a check and they take care of rest right?
Response: In one sense this is a correct, since you are paying an external supplier to provide a complete service outcome. The service can come in the form of an account for a hosted software service, a development platform or a set of virtual infrastructure components without you having to own or manage the physical assets. However, on the other side of coin it is critical to understand that what you are also doing is introducing a new set of players into your existing IT management processes. Just as Young Cosette discovered in the musical Les-Miserables we still have to sweep the floors and take care of business even when we live in the clouds.
[At The End Of The Day - Les Miserables]
At the end of the day you get nothing for nothing Sitting flat on your butt doesn’t buy any bread
And several people join including IT Skeptic and Matthew Hooper with really great insights that I'm in violent agreement with. This a topic I've written about before: What responsibility and visibility does IT need to have when engaging a service provider? Well cloud computing is bringing this issue back to the table with a lot of force.
My response is:
But there are differences worth thinking about with cloudcomputing. As a user of Amazon EC2, I'm running about 81 instances, several hundred gig of data, and multiple vlans.
And it's forced me to think differently about systems. For example, lifecycle management has become way more important than standard system configuration. We have one image, we test the hell out of it, but then the next 80 servers are all the same image. Traditional cms would have me monitor the internals of 80 servers.
Assets are not that useful, because the real issue becomes subscription lifecycle management because of the liability issue. As long as it's on, Amazon bills me.
Capacity management is a non-issue because of the elasticity, but I better have a good contact at the provider.
Monitoring also becomes different. My cloud is a black box beyond a certain point, but I can monitor uptime, performance. But really, I can't do anything about the machine, OS, Storage and Network. In fact, I build that lack of knowledge into the app architecture -- an instance will fail, so I build that assumption and not worry when it does fail. I report no problem and do no root cause analysis on that part of the infrastructure. I do it on my application, of course.
So my take is: the old stuff applies but the emphasis will be very different than in-house IT.
And yes, I'll provide a song to end with a cloud motif, Paper Planes by MIA!
No one on the corner has swagger like us
Hit me on my Burner prepaid wireless
We pack and deliver like UPS trucks
Already going hell just pumping that gas