Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Extending Puppet
  • Table Of Contents Toc
Extending Puppet

Extending Puppet

By : Alessandro Franceschi
4.9 (16)
Buy this Book
close
close
Extending Puppet

Extending Puppet

4.9 (16)
By: Alessandro Franceschi
Buy this Book

Overview of this book

This book is a clear, detailed and practical guide to learn about designing and deploying you puppet architecture, with informative examples to highlight and explain concepts in a focused manner. This book is designed for users who already have good experience with Puppet, and will surprise experienced users with innovative topics that explore how to design, implement, adapt, and deploy a Puppet architecture. The key to extending Puppet is the development of types and providers, for which you must be familiar with Ruby.
Table of Contents (14 chapters)
close
close
close
Preface
Icon
Preface
Icon
What this book covers
Icon
What you need for this book
Icon
Who this book is for
Icon
Conventions
Icon
Reader feedback
Icon
Customer support
Lock Free Chapter
1
1. Puppet Essentials
Icon
1. Puppet Essentials
Icon
The Puppet ecosystem
Icon
Puppet components
Icon
Installation and configuration
Icon
Puppet in action
Icon
Summary
2
2. Hiera
Icon
2. Hiera
Icon
Installing and configuring Hiera
Icon
Working with the command line on a YAML backend
Icon
Using Hiera in Puppet
Icon
Additional Hiera backends
Icon
Using Hiera as an ENC
Icon
Summary
3
3. PuppetDB
chevron up
Icon
3. PuppetDB
Icon
Installation and configuration
Icon
Dashboards
Icon
The PuppetDB API
Icon
Querying PuppetDB for fun and profit
Icon
The puppetdbquery module
Icon
How Puppet code may change in the future
Icon
Summary
4
4. Designing Puppet Architectures
Icon
4. Designing Puppet Architectures
Icon
The components of Puppet architecture
Icon
The Foreman
Icon
Roles and profiles
Icon
The data and the code
Icon
Sample architectures
Icon
Summary
5
5. Using and Writing Reusable Modules
Icon
5. Using and Writing Reusable Modules
Icon
The evolution of modules' layouts
Icon
The parameters dilemma
Icon
Reusability patterns
Icon
Summary
6
6. Higher Abstraction Modules
Icon
6. Higher Abstraction Modules
Icon
Understanding the need for higher abstractions
Icon
The OpenStack example
Icon
An approach to reusable stack modules
Icon
Summary
7
7. Deploying and Migrating Puppet
Icon
7. Deploying and Migrating Puppet
Icon
Examining the potential scenarios and approaches
Icon
Patterns for extending Puppet coverage
Icon
Things change
Icon
Summary
8
8. Code Workflow Management
Icon
8. Code Workflow Management
Icon
Writing the Puppet code
Icon
Git workflows
Icon
Code review
Icon
Testing the Puppet code
Icon
Deploying the Puppet code
Icon
Propagating Puppet changes
Icon
Puppet Continuous Integration tools
Icon
Summary
9
9. Scaling Puppet Infrastructures
Icon
9. Scaling Puppet Infrastructures
Icon
Scaling Puppet
Icon
Scaling stored configs
Icon
Measuring performance
Icon
Summary
10
10. Writing Puppet Plugins
Icon
10. Writing Puppet Plugins
Icon
Anatomy of a Puppet run, under the hood
Icon
Custom report handlers
Icon
Custom faces
Icon
Summary
11
11. Beyond the System
Icon
11. Beyond the System
Icon
Puppet on a network equipment
Icon
Puppet for cloud and virtualization
Icon
Puppet on storage devices
Icon
Summary
12
12. Future Puppet
Icon
12. Future Puppet
Icon
Introducing the future parser
Icon
Other new features
Icon
Improved error system
Icon
Data in modules
Icon
Facter 2
Icon
Trapperkeeper
Icon
Summary
13
Index
Icon
Index

Chapter 3. PuppetDB

A model based on agents that receive and apply a catalog received from the Puppet Master has an intrinsic limitation. The client has no visibility and direct awareness about the state of resources of the other nodes.

It is not possible, for example, to execute functions that do different things according to different external conditions, during the catalog application. There are many cases where information about other nodes and services could be useful to manage local configurations. For example, we might have to perform the following actions:

  • Start a service only when we are sure that the database, the queues, or any external resource it relies upon are already available in some external nodes
  • Configure a load balancer that dynamically adds new servers, if they exist
  • Manage the setup of a cluster; this setup involves specific sequences of commands to be executed in a certain order on different nodes

The declarative nature of Puppet's DSL might look inappropriate...

CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Extending Puppet
End of Section 3
Next Section
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful
Order Page Read Now

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon