Book Image

Puppet 4.10 Beginner's Guide - Second Edition

By : John Arundel
Book Image

Puppet 4.10 Beginner's Guide - Second Edition

By: John Arundel

Overview of this book

Puppet 4.10 Beginner’s Guide, Second Edition, gets you up and running with the very latest features of Puppet 4.10, including Docker containers, Hiera data, and Amazon AWS cloud orchestration. Go from beginner to confident Puppet user with a series of clear, practical examples to help you manage every aspect of your server setup. Whether you’re a developer, a system administrator, or you are simply curious about Puppet, you’ll learn Puppet skills that you can put into practice right away. With practical steps giving you the key concepts you need, this book teaches you how to install packages and config files, create users, set up scheduled jobs, provision cloud instances, build containers, and so much more. Every example in this book deals with something real and practical that you’re likely to need in your work, and you’ll see the complete Puppet code that makes it happen, along with step-by-step instructions for what to type and what output you’ll see. All the examples are available in a GitHub repo for you to download and adapt for your own server setup.
Table of Contents (20 chapters)
Puppet 4.10 Beginner's Guide Second Edition
About the Author
About the Reviewer
Customer Feedback

Distributing Puppet manifests

So far in this book, we've only applied Puppet manifests to one node, using puppet apply with a local copy of the manifest. To manage several nodes at once, we need to distribute the Puppet manifests to each node so that they can be applied.

There are several ways to do this and, as we saw in Chapter 1, Getting started with Puppet, one approach is to use the agent/master architecture, where a central Puppet master server compiles your manifests and distributes the catalog (the desired node state) to all nodes.

Another way to use Puppet is to do without the master server altogether, and use Git to distribute manifests to client nodes, which then run the puppet apply command to update their configuration. This stand-alone Puppet architecture doesn't require a dedicated Puppet master server, and there's no single point of failure.

Both agent/master and stand-alone architectures are officially supported by Puppet, and it's possible to change from one to the other...