Book Image

Puppet 3: Beginner's Guide

By : John Arundel
Book Image

Puppet 3: Beginner's Guide

By: John Arundel

Overview of this book

<p>Everyone's talking about Puppet, the open-source DevOps technology that lets you automate your server setups and manage websites, databases, and desktops. Puppet can build new servers in seconds, keep your systems constantly up to date, and automate daily maintenance tasks. <br /><br />"Puppet 3 Beginner's Guide" gets you up and running with Puppet straight away, with complete real world examples. Each chapter builds your skills, adding new Puppet features, always with a practical focus. You'll learn everything you need to manage your whole infrastructure with Puppet.<br /><br />"Puppet 3 Beginner’s Guide" takes you from complete beginner to confident Puppet user, through a series of clear, simple examples, with full explanations at every stage.</p> <p>Through a series of worked examples introducing Puppet to a fictional web company, you'll learn how to manage every aspect of your server setup. Switching to Puppet needn't be a big, long-term project; this book will show you how to start by bringing one small part of your systems under Puppet control and, little by little, building to the point where Puppet is managing your whole infrastructure.</p> <p>Presented in an easy-to-read guide to learning Puppet from scratch, this book explains simply and clearly all you need to know to use this essential IT power tool, all the time applying these solutions to real-world scenarios.</p>
Table of Contents (17 chapters)
Puppet 3 Beginner's Guide
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Summary


A quick rundown of what we've learned in this chapter.

Reporting

You can get a summary report of what Puppet did on its run by using the --summarize flag with puppet apply. For more detailed reporting, enable reports by setting report=true in /etc/puppet/puppet.conf.

Puppet will write report files to (by default, but you can change this) /var/lib/puppet/reports, in a directory named after the machine's hostname. Each report file will be named according to the date and time of the Puppet run it covers.

Puppet's report files include some summary data about the run itself, and how many resources were found to be out of sync with the manifest. This is followed by a detailed list of all the resources on the server and the number of properties that were changed or out of sync for each resource.

If any resource was changed, the report will include details of each property that was changed, with its previous value and updated value.

Debug and dry-run modes

When you don't need a full report, but...