A while back, I was starting up an EC2 instance on the AWS cloud when it entered an endless restart loop. All the application deployment efforts we’d made (installation and service configuration) over two weeks just went down the drain. So we called support. The support rep redirected us to his team leader who simply told us that, as indicated in the SLA, we had to abide by the shared responsibility model and they were not liable for our loss.
The Shared Responsibility Model – Shared Responsibility refers to the responsibility of the cloud vendor, as well as the cloud consumer, to make sure that everything is backed up and appropriately configured to avoid situations like the one we were in. In short, it was our fault for not having better programmed our architecture.
While investing in building new data centers all over the world and creating the management overlay in order to be able to sell their hardware, IaaS operators are also relying on their ecosystem to support the evolving enterprises that go to the cloud (e.g. the “Enterprise Grade Cloud”).
API First – The move to the cloud pushes the data center to re-invent itself within the new environment. It is a fact that, although the cloud is a pure revolution (at least in MHO), terms such as SLA, TCO and ROI are still valid in this new IT era. Thanks to industry leaders such as Salesforce.com that realize the notion of “API first”, vendors such Amazon cloud present new capabilities first through their APIs. In this way, the cloud operator platform enables development of its ecosystem.
Something that amuses me is the fact that 80% of so-called “Introduction to AWS” stuff is mainly geared at EC2. While I don’t have any problem with it, I think they’re missing the main point in Cloud as a full stack platform, which is to manage more and maintain less.
Let me explain this further: I’m a huge fan of NoOps, even before the name was coined. What we’ve learnt from using AWS Services like S3, Dynamo, and the SNS/SQS Sisters, is that managers actually LOVE not having to consider additional servers to maintain. But how did we get to this point?
The benefits of migrating workloads between different cloud providers or between private and public clouds can only truly be redeemed with an understanding of the cloud business model and cloud workload management. It seems that cloud adoption has reached the phase where advanced cloud users are creating their own hybrid solutions or migrating between clouds while striving to achieve interoperability values within their systems. This article aims to answer some of the questions that arise when managing cloud workloads.
Dear IAmOnDemand reader, I would like to personally invite you to join an interesting webinar that will take place this Wednesday, April 3rd.
As part of my job at Newvem, I have assembled a power-house panel of some of the top thought-leaders in cloud computing to discuss the importance of a healthy cloud, focusing on cost efficiency, risk tolerance, and resource optimization.
This is the story of a veteran software development company and their adoption of the cloud. This research is presented in two parts.
The first part is based on an interview with Mr. Igal Korach, Director of Cloud Services at ClickSoftware. It describes the company’s cloud adoption from the perspective of deployment and operations including processes and tools.
The second part of this research below, is based on a conversation with Mr. Udi Keidar, VP of Cloud Services at ClickSoftware. In this post, I will present some interesting business views of a company that, for years, has been successfully delivering its software to the billion dollar enterprise market. I will discuss the disruptive changes this innovative software company experienced regarding sales methodologies, delivery, pricing, and the future direction of their business.
Last month I attended HP Discover (disclosure: my participation was funded by Ivy World). The IT war already started however HP stands still not taking initiatives and real risks as true leaders should take. At the three-day conference I learned why some companies don’t last and why this IT giant is at a great risk of losing in this new era IT battle. This is a story of a lasting company that might have already lost.
> > > HP’s Washes the Cloud