Sign In Start Free Trial

Puppet 5 Cookbook

By : Thomas Uphill

3.7 (3)

Puppet 5 Cookbook

3.7 (3)

By: Thomas Uphill

Overview of this book

Puppet is a configuration management system that automates all your IT configurations, giving you control of managing each node. Puppet 5 Cookbook will take you through Puppet's latest and most advanced features, including Docker containers, Hiera, and AWS Cloud Orchestration. Updated with the latest advancements and best practices, this book delves into various aspects of writing good Puppet code, which includes using Puppet community style, checking your manifests with puppet-lint, and learning community best practices with an emphasis on real-world implementation. You will learn to set up, install, and create your first manifests with version control, and also learn about various sysadmin tasks, including managing configuration files, using Augeas, and generating files from snippets and templates. As the book progresses, you'll explore virtual resources and use Puppet's resource scheduling and auditing features. In the concluding chapters, you'll walk through managing applications and writing your own resource types, providers, and external node classifiers. By the end of this book, you will have learned to report, log, and debug your system.

Preface

Preface

Who this book is for

What this book covers

To get the most out of this book

Sections

Get in touch

Free Chapter

Puppet Language and Style

Puppet Language and Style

Introduction

Adding a resource to a node

Using facter to describe a node

Using puppet facts

Installing a package before starting a service

Installing, configuring, and starting a service

Using community Puppet style

Installing Puppet

Creating a manifest

Checking your manifests with puppet-lint

Making modules

Using standard naming conventions

Using inline templates

Iterating over multiple items

Writing powerful conditional statements

Using regular expressions in if statements

Using selectors and case statements

Using the in operator

Using regular expression substitutions

Puppet 5 changes

Puppet 4/5 changes

Puppet Infrastructure

Puppet Infrastructure

Introduction

Managing your manifests with Git

Creating a decentralized Puppet architecture

Writing a papply script

Running Puppet from cron

Bootstrapping Puppet with bash

Creating a centralized Puppet infrastructure

Creating certificates with multiple DNS names

Setting up the environment

Configuring PuppetDB

Configuring Hiera

Environment-specific Hiera

Setting node-specific data with Hiera

Writing a custom Hiera5 function

Storing secret data with hiera-eyaml

Automatic syntax-checking with Git hooks

Pushing code around with Git

Managing environments with Git

Writing Better Manifests

Writing Better Manifests

Introduction

Using arrays of resources

Using resource defaults

Using defined types

Using tags

Using run stages

Using roles and profiles

Using data types in Puppet

Passing parameters to classes

Passing parameters from Hiera

Writing reusable, cross-platform manifests

Getting information about the environment

Importing dynamic information

Passing arguments to shell commands

Working with Files and Packages

Working with Files and Packages

Introduction

Making quick edits to config files

Editing INI-style files with puppetlabs-inifile

Using Augeas to reliably edit config files

Building config files using snippets

Using ERB templates

Using array iterations in templates

Using EPP templates

Using GnuPG to encrypt secrets

Comparing package versions

Users and Virtual Resources

Users and Virtual Resources

Introduction

Using virtual resources

Managing users with virtual resources

Managing users' SSH access

Managing users' customization files

Using exported resources

Managing Resources and Files

Managing Resources and Files

Introduction

Distributing cron jobs efficiently

Scheduling when resources are to be applied

Using host resources

Using exported host resources

Using multiple file sources

Distributing and merging directory trees

Cleaning up old files

Auditing resources

Temporarily disabling resources

Managing Applications

Managing Applications

Introduction

Using public modules

Managing Apache servers

Creating Apache virtual hosts

Creating NGINX virtual hosts

Managing MariaDB

Creating databases and users

Servers and Cloud Infrastructure

Servers and Cloud Infrastructure

Introduction

Managing firewalls with iptables

Building high-availability services using Keepalived

Managing NFS servers and file shares

Using HAProxy to load balance multiple web servers

Managing EC2 instances

Managing virtual machines with Vagrant

Managing Docker with Puppet

External Tools and the Puppet Ecosystem

External Tools and the Puppet Ecosystem

Introduction

Creating custom facts

Adding external facts

Setting facts as environment variables

Generating manifests with the Puppet resource command

Generating manifests with other tools

Using PDK

Using an external node classifier

Creating your own resource types

Creating your own providers

Creating custom functions

Testing your puppet manifests with rspec-puppet

Monitoring, Reporting, and Troubleshooting

Monitoring, Reporting, and Troubleshooting

Introduction

Noop—the don't-change-anything option

Logging the command output

Logging debug messages

Generating reports

Producing automatic HTML documentation

Drawing dependency graphs

Understanding Puppet errors

Inspecting configuration settings

Other Books You May Enjoy

Other Books You May Enjoy

Leave a review - let other readers know what you think

Customer Reviews

3.7 (3)

5 star

66.7%

4 star

0

3 star

0

2 star

0

1 star

33.3%

Managing users with virtual resources

Users are a great example of a resource that may need to be realized by multiple classes. Consider the following situation. To simplify the administration of a large number of machines, you defined classes for two kinds of user: developers and sysadmins. All machines need to include sysadmins, but only some machines need access to developers:

node 'server' {
  include user::sysadmins
}
node 'webserver' {
  include user::sysadmins
  include user::developers
}

However, some users may be members of both groups. If each group simply declares its members as regular user resources, this will lead to a conflict when a node includes both developers and sysadmins, as in the webserver example.

To avoid this conflict, a common pattern is to make all users virtual resources, defined in a single user::virtual class that every machine...

Search

Your notes and bookmarks