It’s Newton Time! (Part 1)

DZone 's Guide to

It’s Newton Time! (Part 1)

Improvements in getting started documentation and containerization characterize the latest OpenStack, Newton, which came out earlier this month.

· Cloud Zone ·
Free Resource

Oct. 6 marked the calendar for the OpenStack community as release day for OpenStack Newton. To start us off on learning about the OpenStack environment, a great job was done on what I’d say is the OpenStack 1-2-3.

If you go to the OpenStack website, you can scroll down to see these very nicely laid out steps in which we should think about OpenStack as a platform.

Step 1 is to understand how will you use OpenStack by its most fundamental implementation scenarios:

OpenStack Newton powered by projects

This leads us to the second step of finding additional core services that will be put to use by our environment:

OpenStack Newton select core services

Thirdly, we step into the additional projects to discover optional services that will augment our OpenStack environment in order to solve challenges around the big three as I call it: People, Process, and Technology.

OpenStack Newton add optional services

It’s important that we always think logical first, and then physical. Being able to realize what it is that we are trying to solve before we dive into the technical way in which we will solve it ensures that we map our tactical plan to our strategic goals.

Updating the Way We Guide OpenStack Builds

From docs to guides, the transition to a new way of delivering installation and administration guides has also arrived with the Newton release. You can see the updated guides at the Tutorials and Guides site which gives us all of the HTML-driven documentation we will need to stand up an OpenStack Newton environment.

The full docs site for all of the projects is also updated for the latest goodness that has come with the newest OpenStack edition. Using this as your starting point when you wish to look for what’s new, and what the overall OpenStack ecosystem has to offer. Some of the guides have not been updated as much as others where there were less significant changes. Even where there were less changes in the technical documentation, there were some very effective updates to the usability of the guides themselves.

If you want to see a full listing of the changes within the Newton release, there are a nicely compiled list of them right on the documentation site for everyone to review. This is a powerful part of the development around everything within OpenStack. The transparency and collaborative approach ensures that we can all participate.

Containers Get a Bump Up in Magnum

Want to build Kubernetes, Mesos, or Docker Swarm integration? The OpenStack Newton release features more work that is proving itself out as a powerful opportunity to bring container orchestration of any sort into the OpenStack platform. The reason that updates within the newest version of the Magnum project are important is that they allow you to manage your container orchestration, not to orchestrate the containers themselves natively.

It sounds like that is counter to what many projects wish to achieve, but remember that the goal of the Magnum project is to manage the orchestration, not the containers. Let the best-of-breed orchestration tools work as they should, and provide an abstraction to be able to let you not just run the one you want, but to run any of them that will satisfy your requirements.

After all, that’s the whole reason that we have build OpenStack to begin with.

More to Come!

There is really too much to put into a single post, so we will also dive into a few other important updates within the projects. It made sense for me to start with the ones that I have spent a lot more time involved in over the recent months. Look for part two shortly!

openstack ,container ,cloud ,openstack newton

Published at DZone with permission of Eric Wright , DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}