Book Image

Mastering Puppet 5

By : Ryan Russell-Yates, Jason Southgate
Book Image

Mastering Puppet 5

By: Ryan Russell-Yates, Jason Southgate

Overview of this book

Puppet is a configuration management system and a language written for and by system administrators to manage a large number of systems efficiently and prevent configuration drift. The core topics this book addresses are Puppet's latest features and mastering Puppet Enterprise. You will begin by writing a new Puppet module, gaining an understanding of the guidelines and style of the Puppet community. Following on from this, you will take advantage of the roles and profiles pattern, and you will learn how to structure your code. Next, you will learn how to extend Puppet and write custom facts, functions, types, and providers in Ruby, and also use the new features of Hiera 5. You will also learn how to configure the new Code Manager component, and how to ensure code is automatically deployed to (multiple) Puppet servers. Next, you will learn how to integrate Puppet with Jenkins and Git to build an effective workflow for multiple teams, and use the new Puppet Tasks feature and the latest Puppet Orchestrator language extensions. Finally, you will learn how to scale and troubleshoot Puppet. By the end of the book, you will be able to deal with problems of scale and exceptions in your code, automate workflows, and support multiple developers working simultaneously.
Table of Contents (19 chapters)
Title Page
Dedication
Packt Upsell
Contributors
Preface
Index

Separation of concerns between code and data


Hiera separates Puppet DSL from business data, allowing us to use some of the same generic Puppet DSL repeatedly. In fact, as much as 80% of the Puppet DSL most organizations use is entirely generic; only the business data varies. Hiera allows us to make this full separation of concerns between functionality and business data, instead handily passing in the business data to our modules as parameters.

Hiera works by first setting business values at the widest catchment (that is, site-wide, or common in Puppet parlance), and then moving up the hierarchy, overriding this global value at the appropriate level.

Data specific to infrastructure lends itself incredibly well to a hierarchical model. Infrastructure always tends to consist of sets of configurable attributes: IP addresses, ports, hostnames, and API endpoints. There is a ton of settings that we configure within our infrastructures, and most of them are best represented hierarchically.

A lot of...