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.

4 responses to “Debunking A Myth: Are Private Clouds Exclusively Single Tenant?”

  1. Lori MacVittie


    Very nice! I agree in general with the advice to just “do it” and not argue over terminology as well as debunking the myth of single-tenancy in the enterprise.

    I think if you look closely at large organizations you’ll find multi-tenancy is just as easy a fit in an “enterprise” as it is externally. Resources are still shared inside the enterprise, they’re just distributed a bit differently. The lines of demarcation between “tenants” are projects, departments, and lines of business instead of organizations – but they still exist. There is sharing and while the financial benefits may not be as great as in an “external” cloud, they still exist and allow an enterprise to “do more with less”, which is really what we want in the first place.


  2. route_b

    There are cases where an IT infrastructure group with an internal/private cloud could allocate compute resources and their costs based on a economic charge back model for what is actually consumed by a department or division. This seems preferable to the typical head count allocation model commonly used and despised across enterprises.

    In fact our company was working with a major investment bank (unfortunately never implemented as they are no longer the same entity they were…) who were looking to take the payment for computing resources one step further. They were investigating an approach to allocating a shared pool of physical host computers through the use of future and spot market semantics. This approach treated computation as a fungible resource whose ownership could be freely exchanged amongst market participants, i.e., the various, departments and divisions of the bank.

  3. Krish

    Lori and Route_b, Thanks for the comment.

    Lori, that is my point too. I completely agree with it.

    Route_b, thanks for sharing the info. Interesting!!