Join the DZone community and get the full member experience.
Join For FreeDiscover a centralized approach to monitor your virtual infrastructure, on-premise IT environment, and cloud infrastructure – all on a single platform.
Why does OpenStack matter? When I talk with cloud app developers I regularly hear that it doesn't. The cloud conversations center on AWS, Google, Azure, or a platform as a service like Heroku or one based on Docker.
Yet, if you look at current trends you'd see something like:
Or, if you follow the OpenStack community you might see that the US Summit, which happens once per year, went from about 1,800 attendees a year ago to about 4,500 attendees this past May. That's quite a bit of growth year over year.
I don't consider these reasons that OpenStack matters. Rather it matters and these are signs it's worth looking a little deeper into.
What Is OpenStack?
When thinking of OpenStack it's important to put it into perspective compared to the known players like AWS. OpenStack is a platform to build a cloud. Companies like HP can use it to build a product for others or stand up a public cloud. Some others can use it to stand up their own private cloud like Comcast did.
OpenStack is also a community of developers that anyone can join. There are major players pouring piles of money into the project and products in the ecosystem in an effort to make them and it successful.
Cloud Diversity
A regular concern with cloud companies like AWS, Google, or Azure is vendor lock-in. If I'm being honest, I know companies who've wanted to move from one cloud to another but built their application or tooling to be so tightly coupled to a cloud provider they couldn't cost effectively move. This is not uncommon.
With OpenStack the API that works for one provider for a given service works for another provider for that service. Some providers add in their own services or extras but those are generally opt-in features.
Right now there are multiple public cloud providers built using OpenStack. There are more coming that are not listed there. Want to move from one to another? Want to host in two different cloud providers? Want one that's not a US company?
Security
Given all the Snowden revelations there are some who want non-US companies holding their cloud data. Some who want to build their own cloud.
If you're going to build a cloud right now you're doing it with OpenStack. That may be by directly standing it up or by using one of the products that help you with that.
Did you know there are boxes you can plug into a rack of servers and it will stand up OpenStack?
Private Cloud
Most computing isn't in the cloud. While the cloud has taken off there is still far more computing sitting in private data centers. Many of those who operate these private data centers want cloud technologies but can't put their workloads into public clouds.
It's worth taking a moment to talk about why public clouds don't work for everyone. I'll give two of the many reasons.
- There are legal and regulatory reasons. The cases I'm aware of are for our protection.
- Keeping trade secrets in the secret. Industrial espionage happens. Sometimes by governments to give to companies. We don't always live in a kind and gentle world and many organizations take steps to protect against that.
If you're building a private cloud OpenStack has become the top option.
Sometimes you build something in a private cloud and want to move all of it or part of it to a public cloud. If you have the same APIs than the same tooling can be used for both the private and public clouds. The applications can run in both clouds.
These are just a few of the reasons OpenStack matters. The landscape is changing and it's worth paying attention to.
Learn how to auto-discover your containers and monitor their performance, capture Docker host and container metrics to allocate host resources, and provision containers.
Like This Article? Read More From DZone
Published at DZone with permission of Matt Farina , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}