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

The hierarchy


So far, we've only used a single Hiera data source (common.yaml). Actually, you can have as many data sources as you like. Each usually corresponds to a YAML file, and they are listed in the hierarchy section of the hiera.yaml file, in priority order:

hierarchy:
  - name: "Common defaults"
    path: "common.yaml"
  - name: "Source 1"
    path: "source1.yaml"
  - name: "Source 2"
    path: "source2.yaml"
  - name: "Source 3"
    path: "source3.yaml"

It can be helpful to organize Hiera data into separate files; for example, all the configuration relating to web hosts could be stored in a webhost.yaml file. In general, though, you should keep as much data as possible in the common file, simply because it's easier to find and maintain data if it's in one place rather than scattered throughout several files.

Dealing with multiple values

You may be wondering what happens if the same key is listed in more than one Hiera data source. For example, imagine source1.yaml contains the following...