The semiannual OpenStack summit always presents amazing opportunities to not only stay up to date with the latest developments in the ecosystem and help shape its future direction, but also to build and nurture relationships with the amazing community, foundation members and partners who make everything possible.
Every summit sets a new standard, and May’s summit in Vancouver, B.C., centered around the new Kilo release, was no exception. I was very fortunate to be able to be able to speak on the topic of OpenStack high availability, as well as to moderate an operationally focused discussion on the future of containers in an OpenStack world.
In the many conversations I had over the course of the summit, it became clear that there was intense interest around automation, configuration management, and, more specifically, how Puppet plays in both of those spaces. It was so rewarding to be able to talk with so many people, walk them through the basics of the Puppet model and see them grasp how it can enable the management of complex distributed systems like OpenStack.
It was also incredibly validating to see the OpenStack User Survey results. Those of us who deal with Puppet every day couldn't help but notice that, once again, Puppet shows up as the No. 1 choice for deploying production OpenStack environments.
Puppet alone provides the basis for the majority of OpenStack deployments, at 56 percent. Puppet plus deployment tools that utilize Puppet (e.g., Mirantis Fuel, Red Hat OpenStack Platform, PackStack) provide the basis for 72 percent of all production deployments.
There are reasons for this:
Our community has developed a robust and reliable set of modules that provide very clear interfaces for configuring a variety of OpenStack projects. This means that you can be confident in deploying your cloud in a repeatable and testable manner.
What were previously the StackForge Puppet modules are now officially the OpenStack Puppet Modules project. This is clear recognition of the value they bring, as well as the openness and inclusiveness of the community.
We’re very excited about the momentum we have coming out of the Kilo release, and are hard at work preparing for Liberty. I want to extend a big "thank you" to our community, with special recognition for Emilien Macchi, our esteemed (and inaugural) project technical lead, who was integral in orchestrating the integration of the modules into the OpenStack big tent. See you all in Tokyo!
Richard Raseley is a SysOps engineer at Puppet Labs.
- See the OpenStack user survey results: OpenStack users share how their deployments stack up
- Puppet OpenStack modules