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
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
Index

Setting up Hiera


Hiera needs to know one or two things before you can start using it, which are specified in the Hiera configuration file, usually named hiera.yaml (not to be confused with Hiera data files, which are also YAML files; we'll find about those later in this chapter). Each Puppet environment has its own local Hiera config file, located at the root of the environments directory (for example, for the production environment, the local Hiera config file would be /etc/puppetlabs/code/environments/production/hiera.yaml).

Tip

Hiera can also use a global config file located at /etc/puppetlabs/puppet/hiera.yaml, which takes precedence over the per-environment file, but the Puppet documentation recommends you only use this config layer for certain exceptional purposes, such as temporary overrides; all your normal Hiera data and configuration should live in the environment layer.

The following example shows a minimal hiera.yaml file (hiera_minimal.config.yaml):

---
version: 5

defaults:
  datadir...