Learning Puppet 4 covering Puppet 4.4 is now available

By on March 26, 2016 - News Tags: ,

Learning Puppet 4

Learning Puppet 4: A Guide to Configuration Management and Automation

The final, professionally edited book is now available for online reading at Safari Books

Offline versions can be found at:

This book teaches you how to use Puppet 4 for configuration management and automation. If you are new to Puppet and DevOps, this book will walk you through a hands-on learning process.

If you purchase an electronic version, you will receive updates to the book as Puppet evolves.

If you’re a system administrator, developer, or site reliability engineer responsible for handling hundreds or even thousands of nodes in your network, the Puppet configuration management tool will make your job a whole lot easier. This practical guide shows you what Puppet does, how it works, and how it can provide significant value to your organization.

Through hands-on tutorials, I demonstrate how to use Puppet to manage complex and distributed components to ensure service availability. You’ll learn how to secure configuration consistency across servers, clients, your router, and even that computer in your pocket by setting up your own testing environment.

If you are an experienced DevOps engineer, this book covers in detail the changes and improvements in Puppet 4 and how to make best use of them.


Overloaded Geek: writer. devOps engineer. operations architect. motorcycle racer. You can track Jo's experience through Jo's business resume

One Response to “Learning Puppet 4 covering Puppet 4.4 is now available”

  1. iaingblack says:

    Hi Jo 🙂

    I just read the book and got to say it was great. I’ve been trying to pull it all together in my head and you have got me over the line, many thanks!!!

    I just wondered if you had any thoughts on the roles and profiles pattern? Making profiles as a kind of wrapper with defaults to install many modules for a general server application (MySQL + Apache for example) and having hiera override anything environment/node specific isn’t a terrible idea is it? Anything obvious to watch out for? I’m just curious as it’s literally the only thing you didn’t explicitly cover (I think, need to reread, apologies if I missed it). seems to make sense to me but don’t want to go down a wrong path as I start instead of just doing it all in hiera include class definitions and parameters for example?

    Thanks again for such an in depth treatment of everything a newbie could wish to know 🙂

Leave a Reply

You must be logged in to post a comment.