Private Cloud: 'Everyone's got one. Where's yours?'

Private Cloud: 'Everyone's got one. Where's yours?'

Summary: Promising the business a cloud delivered within your own data center, and then failing to provide basic functionality of a cloud, will just make future initiatives and interactions even harder.

SHARE:
TOPICS: Cloud
1

Sound familiar? Executives across the globe feel peer and competitive pressure to “get to yes” on private cloud. This burden falls on IT to provide a cloud solution — oh, and by the way, we need it by the end of the year. With this clock ticking, it’s hard to think about private cloud strategically. In fact, why not to just cloudwash your virtual environment and buy your team time? Many enterprises (yes, even those presenting at events) have gone down this road. And some vendors will suggest this as a short-term fix. DON’T DO IT.

You’re cutting yourself short on what you could achieve with this environment while losing credibility with the business and your peers. Sound overdramatic? The consumerization of IT is forcing IT to connect with the business or risk circumvention. For many, the existing relationship isn't great. And each future interaction could either improve or worsen that relationship. Promising the business a cloud delivered within your own data center, and then failing to provide basic functionality of a cloud will just make future initiatives and interactions even harder. In the meantime, the business will continue to circumvent your department. If you're going to make the invest the resources/time to build this environment and rope in rogue cloud users -- make sure you get to cloud.

Today, cloudwashing is prevalent. But it isn’t always intentional. In fact many truly believe they’ve got a true cloud — especially those using a pre-packaged private cloud software solution. But once you look under the hood it’s hard to miss. These self-proclaimed private clouds often use pieces of the management and automation capabilities but aren’t using the full functionality of these solutions. The most common mistakes?

  1. “Self service access” for a small cloud team, with the business still using a ticket-based system.
  2. Partial automation where IT is still involved in the provisioning of cloud resources. Networking and “security and compliance checks and balances” are the key places where we still see IT involved.
  3. Resource tracking reports not available to the end user and costs associated with usage not presented to the requestor.

Want to find out more about how to get the private cloud right? Come see our session on "How Your Peers Are Getting Private Cloud Right (Or Wrong)" at the Forrester's Infrastructure & Operations Forum 2012 in Vegas later this week.

Topic: Cloud

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Talkback

1 comment
Log in or register to join the discussion
  • Or...does it really matter. Yes it does.

    Lately I've posted a couple of posts about cloudwashing ('Cloud Washing - Don't End Up Washing Your IT with False Clouds' on KnowYourCloud) and if it really matters ('Cloud washing...does it REALLY matter' on my own blog InMaxMind). From the customer perspective: I think the biggest problem is if you THINK you adopted a cloud service but soon realize it is washed and you're in some way locked in. On the other hand; if you know what you're doing and the service fulfill your need it really doesn't matter - but DON'T call it cloud then, there's no need. The problem is that most (non IT pro etc) people can't "judge" before it's too late...and you shouldn't have to be able to judge if the declaration and name of the service says CLOUD. As a cloud adopter you really have to read the T&C's well - it's your responsibility. Consult an advisor or broker if you can't do it on your own.

    I strongly agree with "You???re cutting yourself short on what you could achieve with this environment while losing credibility with the business and your peers." If the customer (internal or external) experience is like above (washed) you as a CSP or internal IT department will lose credibility.

    Don't call it cloud if it doesn't meet the NIST definition.

    @maxbuchler
    maxbuchler