We covered a bit of the operational docs in our first article, but this is a chance to tap into a few of the actual technical features that have landed in Newton. There are also some serious improvements in existing parts of the ecosystem which pack more reliability and resiliency into the infrastructure.
With what could be one of the best documentation notes, the Nova release notes stated “It can be extremely hard to mention all the changes we introduced during that release but we beg you to read at least the upgrade section which describes the required modifications that you need to do for upgrading your cloud from 13.0.0 (Mitaka) to 14.0.0 (Newton). That said, a few major changes are worth to notice here.” If nothing, they should win a prize for that statement alone.
A big focus within this release cycle was around performance and scalability within various projects in the OpenStack platform. Not just scaling out in managing OpenStack nodes, but also just handling the internal supporting infrastructure at all levels. We have seen the growth in OpenStack adoption help to drive the need to find the limits of the OpenStack core infrastructure and push beyond it.
Nova gets a little more live migration love as we see more work around pre-checks and CPU throttling management during migration. It’s also great to see that the Hyper-V RemoteFX capability is being added for Microsoft guests to be able to leverage the better RDP experience. You’ll see Server 2016 sprinkled throughout the documentation which tells us that the demand is there for folks to use OpenStack under their Microsoft Server guest infrastructure as an option.
Neutron gains more fundamentals within it. This is also a big part of laying the groundwork for the eventual (no, for real this time) deprecation of nova-network. Making Neutron simpler to deploy, manage, and configure will help us to get to the point where it is the de facto networking platform in the open source cloud. As the feature set increases, and other plugins and apps that will handle IPAM, NFV, and more, we will see a greater drive in adoption in general for OpenStack.
A More Enterprise-y OpenStack
I’ve said it before, and I’ll say it again. The push to get Enterprise consumers on OpenStack is coming as a result of great innovation by the developers, vendors, and by the consumers themselves. Creating new enterprise-style features has been a long-time wish that is being executed with capabilities such as live migration, high availability, and more external pluggable options with identity and access management systems.
It helps that we have the discussions around OpenStack are moving towards workloads and orchestration of containers within an OpenStack platform. We are seeing opportunities arise for injecting event-driven architectures, PaaS, containers, and traditional VM instances all in the same place. Why not, right? It feels like we have finally evolved past the idea around arguing over pets versus cattle.
APIs are being strengthened up and features are coming across the board on all projects. The REST API is the right place to do these updates as we enable other platforms to consume and control OpenStack resources easily via the API. Long live the loosely-coupled infrastructure!
If you are heading to the OpenStack summit in Barcelona, have fun! If you read this after you get back, feel free to share your thoughts on what you saw there. Happy Stacking!