Book Image

Puppet 8 for DevOps Engineers

By : David Sandilands
Book Image

Puppet 8 for DevOps Engineers

By: David Sandilands

Overview of this book

As DevOps and platform engineering drive the demand for robust internal development platforms, the need for infrastructure configuration tools has never been greater. Puppet, a powerful configuration management tool, is widely used by leading enterprises and boasts a thriving open source community. This book provides a comprehensive explanation of both the Puppet language and the platform. It begins by helping you grasp the basic concepts and approach of Puppet as a stateful language, and then builds up to explaining how to structure Puppet code to scale and allow flexibility and collaboration among teams. As you advance, you’ll find out how the Puppet platform allows the management and reporting of infrastructure configuration. The book also shows you how the platform can be integrated with other tooling, such as ServiceNow and Splunk. The concluding chapters help you implement Puppet to fit in heavily regulated and audited environments as well as modern hybrid cloud environments. By the end of this book, you’ll have gained a solid understanding of the capabilities of both the Puppet language and platform, and you will have learned how to structure and scale Puppet to create a platform to provide enterprise-grade infrastructure configuration.
Table of Contents (22 chapters)
1
Part 1 – Introduction to Puppet and the Basics of the Puppet Language
7
Part 2 – Structuring, Ordering, and Managing Data in the Puppet Language
12
Part 3 – The Puppet Platform and Bolt Orchestration
17
Part 4 – Puppet Enterprise and Approaches to the Adoption of Puppet

Summary

In this chapter, we showed how Bolt complements Puppet’s state-based management by providing a capability to run ad hoc actions for anything that doesn’t fit the declarative enforcement methods of Puppet. We also showed how transports provide the ability for Bolt to connect to targets. We saw how, using the Bolt commands via Unix or PowerShell, we could run commands, scripts, Puppet code, and manifests on targets, as well as uploading and downloading files. We reviewed how Bolt logs to bolt-debug.log and how to configure logging to get more logs for different issues.

We then showed how Bolt projects provide a directory structure to contain the configuration and data for Bolt. Bolt projects provide the inventory.yaml file to contain target and transport configuration and the bolt-project.yaml file to contain project-level configuration settings for Bolt and to allow module dependencies to be downloaded into the project. We discussed how the Bolt project is loaded...