10 Mistakes to Avoid in Planning for OpenStack Cloud

If you’ve spent quality time working on open source and cloud infrastructure, you’ve likely heard some whoppers. We have. I’ve often found myself in meetings and on concalls thinking, “You’re going to what?”

After a little while, it was impossible not to make a list of these well-meant misconceptions I’ve heard from customers, prospects and other stakeholders, which was published this past week at CitizenTekk. And yes, the names have been deleted to protect the innocent.

More importantly, you may hear some of these yourself. Take a deep breath. This stuff is new, and it changes fast, and not everyone is going to get it right the first time. (Some, of course, will need more than once or twice). Here’s the list, ranked by how high I raise my eyebrows when I hear them.

  • Mistake #10: It’s open source. Who needs a budget?
  • Mistake #9: I can do it by myself.
  • Mistake #8: Everyone understands the terminology.
  • Mistake #7: Assume legacy systems will go away (or be migrated).
  • Mistake #6: All you need is load balancing.
  • Mistake #5: We don’t need to talk to the developers.
  • Mistake #4: Our staff has the skills.
  • Mistake #3: We can monetize later.
  • Mistake #2: The cloud fixes itself.
  • Mistake #1: Failure is not an option.

You can read the full article here.

Subscribe to Our Newsletter

Latest Tweets

Suggested Content

LIVE DEMO
Mirantis Cloud Platform
WEBINAR
Machine Learning in the Datacenter