OpenStack Project Status October

OpenStack Project Status October

6 November 2014 by in OpenStack

It’s now the first week of November. Several members of our OpenStack team are currently in Paris attending the OpenStack Summit and our restricted beta test has finally started on our future production platform. We’ll tell you all about both of these things soon, but first we look back at what has been achieved last month.

The big news, of course, was the release of the new stable OpenStack release Juno. It has some major improvements that we were anxiously waiting for which improve availability and reliability as well as new features and supported services. We’re still testing the upgrade path and plan, once we start our public beta, to have the entire platform running on the new Juno release.

In order to start testing our platform and services with members not part of our project team, we wanted to be sure that no major bugs and problems remained on our production environment. Although it may be a beta test, we want to give our testers a platform that’s relatively bug free, doesn’t crash on a regular basis and should, basically, just work. It took us longer than expected to get to that point, but October proved to be the month in which we were able to get there. Configuration-wise, we’re at the point where we can safely deploy and redeploy parts of our platforms without breaking it. We also fixed some remaining issues we had related to networking and made lots of progress in automation of business processes that use the different API’s and messaging queues.

Although we primarily plan to deliver our OpenStack platform as an IaaS service, we understand that the real power lies in its ability to easily and quickly build PaaS solutions. That’s why we consider orchestration using OpenStack’s Heat tool to be an important part of the functionality we wish to offer to our customers. Since we’re as good as done with the basic functionality and object storage, testing Heat will be our next major focus.

Besides the platform itself, our new website and community will need to be up and running once our public beta starts. The non-public version has been launched, focused on helping people get started and giving us the feedback we need to solve bugs and improve the website and platform itself. We’re optimizing tutorials and improving navigation and functionality of the user community.

Call me back