Skip to content

OpenStack Launches the Next Generation of Private Clouds

The OpenStack Foundation has launched its platform’s latest version that makes it possible for enterprises to use cloud computing platforms, which are AWS-like, for their data centers. The 15th OpenStack release – Ocata, comes after a relatively short release cycle of only 4 months. The usual release cycle is 6 months long. Thanks to this shorter release cycle, you are able to focus your attention on stability rather than the features’ associated issues and opportunities.

It goes without saying that OpenStack is both a massive and an impressive project, which includes more than twenty sub-projects. You need to provide updates for all of the projects included, of course. In addition, it has become obvious that the majority of new features pays a great deal of attention to the improved support reserved for OpenStack software containers. As a result, the container-oriented projects get all the attention and develop much faster compared with other projects.

When it comes to Ocata release, these improvements in the field of container support strongly contribute to the much efficient integration, which includes both Kubernetes and Kolla. The aim is to make it easier to conduct a deployment on containers. You actually hit two targets with one arrow and that’s to ensure easier deployment and less complicated upgrades. Additional updates include improved Mesosphere support in Magnum and Docker Swarm support associated with the networking service for the Kuryr containers.

What’s happening in the relationship between OpenStack and container engines? There were some concerns that the containers shouldn’t be OpenStack’s focus. However, it has become obvious that these concerns were overblown and as a result, we have containers as the integral project’s part.

Regarding the OpenStack’s future and new perspectives, we can notice some major shifts in the ways how enterprises treat their needs associated with private clouds.

The first private cloud generation wasn’t easy to use. You had to have more people at your disposal and the proper adoption patterns. For instance, Walmart and PayPal to adopt it with success. Though it was easy for these business giants to deal with these requirements, the “mortal ones” had no other choice than to wait for some better times. Now, the next generation allows you to go easy on the number of people required. More importantly, you don’t need impressive business ecosystems to see it work.

So, the first private cloud generation was reserved for big teams and huge companies. Nowadays, thanks to these changes, we are free to predict that privacy clouds can match the price and effectiveness of the huge public cloud services, such as Auro among others. It is really great to be able to enjoy the flexibility of these systems for an affordable price, which is exactly what OpenStack is doing right now.

 

 

One Comment

  1. […] OpenStack was initially attractive to clients due to the fact that Amazon Web Services enabled an entirely unique way of operation. While it was innovative, its utter dependency on AWS made it weak. The problems that arose were technologically and financially based. AWS tries to cut prices, but the larger you grow, the more incremental cost increases occur. And at that point, if you decide you want to switch, you are going to find yourself stuck, as your complete infrastructure is constructed around AWS products and APIs. […]

Leave a Reply

Your email address will not be published. Required fields are marked *