Completing the stack with PuppetDB
by Thomas Uphillis, Jaime Soriano Pastor, Alessandro Franceschi, Martin Alfke, Feli
Puppet: Mastering Infrastructure Automation
- Puppet: Mastering Infrastructure Automation
- Table of Contents
- Puppet: Mastering Infrastructure Automation
- Puppet: Mastering Infrastructure Automation
- Credits
- Preface
- 1. Module 1
- 1. Writing Your First Manifests
- 2. The Master and Its Agents
- 3. A Peek under the Hood – Facts, Types, and Providers
- 4. Modularizing Manifests with Classes and Defined Types
- 5. Extending Your Puppet Infrastructure with Modules
- An overview of Puppet's modules
- Maintaining environments
- Building a specific module
- Naming your module
- Making your module available to Puppet
- Implementing basic module functionality
- Creating utilities for derived manifests
- Enhancing the agent through plugins
- 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
- Summary
- 6. Leveraging the Full Toolset of the Language
- 7. New Features from Puppet 4
- 8. Separating Data from Code Using Hiera
- 2. Module 2
- 1. Puppet Essentials
- The Puppet ecosystem
- Puppet components
- Installing and configuring Puppet
- Puppet in action
- Variables, facts, and scopes
- Meta parameters
- Managing order and dependencies
- Reserved names and allowed characters
- Conditionals
- Comparison operators
- Iteration and lambdas
- Exported resources
- Modules
- Restoring files from a filebucket
- Summary
- 2. Managing Puppet Data with Hiera
- 3. Introducing PuppetDB
- 4. Designing Puppet Architectures
- 5. Using and Writing Reusable Modules
- 6. Higher Abstraction Modules
- 7. Puppet Migration Patterns
- 8. Code Workflow Management
- 9. Scaling Puppet Infrastructures
- 10. Extending Puppet
- 11. Beyond the System
- 12. Future Puppet
- 1. Puppet Essentials
- 3. Module 3
- 1. Dealing with Load/Scale
- 2. Organizing Your Nodes and Data
- 3. Git and Environments
- 4. Public Modules
- 5. Custom Facts and Modules
- 6. Custom Types
- 7. Reporting and Orchestration
- 8. Exported Resources
- 9. Roles and Profiles
- 10. Troubleshooting
- A. Bibliography
- Index
Whether you choose to use puppetserver or prefer Passenger after all, there is yet another piece of infrastructure that should be considered for each master host. PuppetDB is a specialized database designed to interact with the Puppet master. It mainly comprises a PostgreSQL backend with an API wrapper. The latter was written in Clojure and runs in yet another JVM.
PuppetDB aids the master's secondary task of storing reports and other agent data. It is also necessary for some specific manifest compiler functionality. This is covered in Chapter 6, Leveraging the Full Toolset of the Language.
The best way to set up and configure PuppetDB is actually Puppet itself. Since the necessary tools have not yet been introduced, we will postpone this step until Chapter 6, Leveraging the Full Toolset of the Language. This is not a problem, because PuppetDB is not essential for basic master operation.
-
No Comment