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

Beyond Hiera using Jerakia


If you would like to transcend single-customer and small-scale hierarchical data classifications and open up the possibilities of modeling larger, more complex and diverse environments, you should consider the use of Jerakia (http://jerakia.io), using Jerakia as a Hiera backend, or configuring Puppet to accept Jerakia as a data-binding terminus.

Jerakia advanced use cases

Here are some questions around advanced use cases for Jerakia:

  • How can I use a different Hiera backend for just one module?
  • How can I allow a team the use of a separate hierarchy, exclusively for their own application?
  • How can I allow access to a smaller subset of data to a certain user or team?
  • How can I use eyaml encryption without being forced to use YAML?
  • How can I implement a dynamic hierarchy rather than hard coding it?
  • How can I group together application-specific data into separate YAML files?

Jerakia allows us to implement some of these corner cases.

Installing Jerakia

Jerakia is installed from...