An introduction to Puppet, an infrastructure configuration management tool. In this article Susannah Axelrod, gives an overview of both Puppet, the language, and Puppet, the platform, discussing all the main concepts around them. Susannah also writes about how to start an Infrastructure as Code initiative as well as sharing additional learning resources for those who want to know Puppet in-depth.
“Infrastructure as Code” is a tenet of the DevOps community. But treating Infrastructure as Code is a tall order. Development practices have also evolved rapidly and nowadays that means continuous integration, automated tests and more. We’ll make a brief introdution to Chef, a well-known IT automation tool, and use it to illustrate the state of the art.
Overall the book is a quick read that provides some useful insights and potential starting points for enterprise practitioners and technical managers in medium to large enterprises where development and operations are still very defensive towards each other (often driven by conflicting goals) and where a blame culture reigns.
InfoQ reached out to experienced ops engineers to ask them what is “Immutable Infrastructure”, its borders as well as its benefits and drawbacks, in particular compared to desired state convergence. 1
In this article you will find guidance on how to get started realizing a Continuous Delivery vision, especially in the context of existing development and release environments in large enterprises.