Book Image

Puppet 5 Essentials - Third Edition

By : Martin Alfke, Felix Frank

Book Image

Puppet 5 Essentials - Third Edition

By: Martin Alfke, Felix Frank

Overview of this book

Puppet is a configuration management tool that allows you to automate all your IT configurations, giving you control over what you do to each Puppet Agent in a network, and when and how you do it. In this age of digital delivery and ubiquitous Internet presence, it's becoming increasingly important to implement scaleable and portable solutions, not only in terms of software, but also the system that runs it. This book gets you started quickly with Puppet and its tools in the right way. It highlights improvements in Puppet and provides solutions for upgrading. It starts with a quick introduction to Puppet in order to quickly get your IT automation platform in place. Then you learn about the Puppet Agent and its installation and configuration along with Puppet Server and its scaling options. The book adopts an innovative structure and approach, and Puppet is explained with flexible use cases that empower you to manage complex infrastructures easily. Finally, the book will take readers through Puppet and its companion tools such as Facter, Hiera, and R10k and how to make use of tool chains.

Preface

What this book covers

What you need for this book

Who this book is for

Reader feedback

Customer support

Free Chapter

Writing Your First Manifests

Writing Your First Manifests

Getting started

Introducing resources, parameters, and properties

Interpreting output of the puppet apply command

Using variables

Adding control structures in manifests

Controlling the order of execution

Implementing resource interaction

Examining Puppet core resource types

Puppet Server and Agents

Puppet Server and Agents

The Puppet server

Setting up the Puppet agent

Performance optimizations

Completing the stack with PuppetDB

A Peek into the Ruby Part of Puppet - Facts, Types, and Providers

A Peek into the Ruby Part of Puppet - Facts, Types, and Providers

Putting it all together - collecting system information with Facter

Accessing and using fact values

Extending Facter with custom facts

Simplifying things using external facts

Goals of Facter

The resource type's life cycle on the agent side

Command execution control with providers

Summarizing types and providers

Combining Resources in Classes and Defined Types

Combining Resources in Classes and Defined Types

Introducing classes and defined types

Design patterns

Including classes from defined types

Ordering and events among classes

Ordering containers

Making classes more flexible through parameters

Combining Classes, Configuration Files, and Extensions into Modules

Combining Classes, Configuration Files, and Extensions into Modules

The contents of Puppet's modules

Managing environments

Building a component module

Replacing a defined type with a native type

Enhancing Puppet's system knowledge through facts

Refining the interface of your module through custom functions

Making your module portable across platforms

Finding helpful Forge modules

The Puppet Beginners Advanced Parts

The Puppet Beginners Advanced Parts

Building dynamic configuration files

Managing file snippets

Using virtual resources

Cross-node configuration with exported resources

Setting defaults for resource parameters

Avoiding antipatterns

New Features from Puppet 4 and 5

New Features from Puppet 4 and 5

Upgrading to Puppet 4

Learning lambdas and functions

Creating Puppet 4 functions

Leveraging the new template engine

Handling multiline with HEREDOC

Using Puppet 5 server metrics

Breaking old practices

Separation of Code and Data with Hiera

Separation of Code and Data with Hiera

Understanding the need for separate data storage

Building hierarchical data structures

Fetching data from classes

Debugging data lookups

Managing resources from data

Puppet Roles and Profiles

Puppet Roles and Profiles

Technical component modules

Implementing components in profiles

The business use case and node classification

Building roles from profiles

Placing code on the Puppet server

Customer Reviews

5 star

0

4 star

0

3 star

0

2 star

0

1 star

0

Making your module portable across platforms

Sadly, our Cacti module is very specific to the Debian package. It expects to find the CLI at a certain place and the Apache configuration snippet at another. These locations are most likely specific to the Debian package. It would be useful for the module to work on the Red Hat derivatives as well.

The first step is to get an overview of the differences by performing a manual installation. I chose to test this with a virtual machine running Fedora 18. The basic installation is identical to Debian, except using yum instead of apt-get, of course. Puppet will automatically do the right thing here. The puppet::install class also contains a CLI file, though. The Red Hat package installs the CLI in /var/lib/cacti/cli, rather than /usr/share/cacti/cli.

If the module is supposed to support both platforms, the target location for the remove_device...