Things are moving very fast in OpenStack; it might be useful to take a short break and write down a little bit of retrospective; it will help to see what happened in Puppet OpenStack project during the last months.
Our Vancouver week just ended and I think it was a very productive Summit for the Puppet OpenStack folks. This blog post summarizes what we did this week, and what we plan for the next release.
As OpenStack matures as a solution, there is a growing need to effectively deploy OpenStack in a prescriptive manner. To achieve this, numerous deployers have adopted Puppet to be their configuration tool of choice and it has grown to be the most widely used tool when deploying OpenStack. The community effort to automate the deployment of OpenStack using Puppet has… Read more →
Puppet is a key component in server deployment and configuration automation. When nodes successfully get provisioned by a Puppet master they retrieve all sorts of data, some which might be both confidentials and criticals. It is then mandatory to ensure that only authorized instances or nodes are allowed to retrieve such data. In today elastic systems and cloud era, it… Read more →
If you could not attend the last OpenStack Summit in Atlanta and you are interested by Puppet, this article is for you. First feedback: I was so happy to see dedicated sessions for Automation and OPS subjects. We got plenty of sessions where we could share experiences about the reality of OpenStack in production. Most people present in these sessions… Read more →
Having an industrialized way to deploy OpenStack for our customers, independant of the OpenStack/Linux distributions our customers may chose to use, is a key element to ensure maintainability and upgradability, and therefore customer satisfaction. As our experience grows, our set of tools is getting better everyday, and while we have often described some of these tools individually, providing a complete… Read more →
About OpenStack Puppet modules OpenStack has a lot of projects and all need to be configured to make an infrastructure working as we want. That means we needs one puppet module by project. Like we have in most of modules, each of them is made up of several class definitions, resource declarations, defined resources, and custom types/providers. Multiple companies and… Read more →