Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Mastering Puppet 5
  • Toc
  • feedback
Mastering Puppet 5

Mastering Puppet 5

By : Russell-Yates, Southgate
4.4 (5)
close
Mastering Puppet 5

Mastering Puppet 5

4.4 (5)
By: Russell-Yates, 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 (14 chapters)
close

Puppet Tasks

Puppet is designed to provide continual enforcement of an end-state on nodes in an infrastructure. While Puppet can cover most infrastructure tasks, some things are better left to ad hoc tasks. Puppet Tasks are on-demand actions that can be run on nodes and containers. You write tasks in a similar way to scripts, and they can be written in any language that's available on the target node.  When deciding on the right tool for the job, between a task or a Puppet manifest, I stick to a simple thought process: is this something I want permanently, or a single one-off action? 

Let's think about some things in a normal workplace that would be permanent, or stateful. The physical address of where I work and the building, rooms, and furniture are examples of physical things I'd want permanently enforced. Things like weekly meetings or the daily scrum...

bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete