If you’re like most people, the reason you’re looking at OpenStack for a private cloud is because your developers fell in love with public cloud, and you want to give them the same experience, but with better economics, control, and performance of a private cloud.
The reality is that instead of looking to replicate the public cloud experience, privately, we often run in to people that want to fiddle with every aspect of the infrastructure and OpenStack® itself.
Companies start off looking for a public cloud experience, but quickly become more interested in the choice of hypervisor, network models and storage architecture -- none of which are even up for discussion in a public cloud. These questions aren’t wrong to ask, they just shouldn’t matter to you. What should matter is the experience your developers will have in your private cloud,
how your apps will run, and how your private cloud will integrate with your existing systems and apps.
The only exception to the above rule should be if you have a use case or apps that just wouldn’t work in a public cloud, because these apps won’t work in a private cloud, either. You’ll have to
build yourself a custom infrastructure that you may call “cloud,” but likely will just be using some cloud technology and won’t resemble a cloud at all when you’re done. Luckily, the number of
companies that need to go that route is very small.
After talking to thousands of people about their private cloud journey, we’ve created a simple checklist on the next page to help you determine if you’re ready for an OpenStack® private cloud. Check the boxes that apply to you, and add up your score! And when you’re ready to get started, Cisco can help!