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.

2 responses to “Defining Federated Cloud Ecosystems”

  1. Steve Caughey

    Krishnan,

    I’m in agreement here – I think that increasingly organisations and individuals will be consuming services which are delivered utilising resources owned by multiple providers in a federated network.

    To me the key facets of a federated cloud are autonomy and cooperaion. The organisations who own the resources being utilised, and the services they deliver, are in ultimate control of their own environments and cooperate through agreement with other parties. At Arjuna, we argue that service agreements will be the glue that connects this network together. Those agreements will define not only the form of the service being delivered and its QoS but also potentially a myriad of other aspects, such as support levels, data secuirty, legal juridiction, pricing etc. I’ve blogged recently on this here – http://blog.arjuna.com/2011/10/11/service-agreements-in-the-cloud/

    Steve Caughey, CEO, Arjuna technologies

  2. Equinix Announces Marketplace: Will It Help Federated Cloud Ecosystems?

    […] marketplace idea in the context of federated cloud ecosystem is nothing new. Zimory tried to do it long before many in the industry became aware of this cloud […]