Articles in this series

LinkedIn Twitter
Director, OpenShift Strategy at Red Hat. Founder of Rishidot Research, a research community focused on services world. His focus is on Platform Services, Infrastructure and the role of Open Source in the services era. Krish has been writing @ CloudAve from its inception and had also been part of GigaOm Pro Analyst Group. The opinions expressed here are his own and are neither representative of his employer, Red Hat, nor CloudAve, nor its sponsors.

6 responses to “Two Events That “Clouded” Our Thinking In 2011”

  1. koolhead17


    I was interested to know more about Eucalyptus and Openstack. 🙂

  2. Nati Shalom

    Hi Krishnan
    I’ve been following your coverage on the PaaS market for a while and found it fairly useful and insightful – this post is of no exception – thanks!

    “The shift in the thinking about the enterprise cloud consumption also poured water into the “DevOps” concept advocated by vendors and pundits with their foot in the IaaS world.”

    I personally believe that rather than looking at the two paradigms DevOps (Automation), PaaS (Platform) as two competing alternatives the shift should be to combine the two.

    Christoper Knee, Vice President, Cloud Computing at VMware summarize it pretty well in his post: DevOps and PaaS – Friend or Foe?

    “What if you could get a PaaS that wasn’t a black box, enabling developers to deploy apps easily while still giving SysAdmins the ability to provision any services they needed (a la Cloud Foundry)?”

    IMO CloudFoundary does part of that and the work that were doing with Cloudify follows that line of thought even more.

    I wrote a more detailed response on the subject on my blog:

    I would appreciate your thoughts on that regard..

  3. Adron

    I’m late on this article… but…

    I must disagree, at least at this point, with the idea that PaaS removes the need for the DevOps Culture. It’ll still be there… legacy/traditional IT is in deep trouble anyway one looks at it. PaaS provides a higher abstraction, this is true, but it doesn’t remove the need for understanding the underlying pieces – which happens anywhere. Especially on things that do need scalability, high availability, etc. Because in the end, on PaaS, straight to IaaS or whatever, somebody has to figure out how to make the scalability and availability possible. Just sticking something on a PaaS doesn’t automatically do that.

    Anyway… we ought to discuss in more detail. I’m intrigued by the prospect.