PuppetDB 3.2 » Overview
PuppetDB collects data generated by Puppet. It enables advanced Puppet features like exported resources, and can be the foundation for other applications that use Puppet’s data.
Install It Now
To start using PuppetDB today:
- Review the system requirements below (and, optionally, our scaling recommendations).
- If you’d like to migrate existing exported resources from your ActiveRecord storeconfigs database, please see the documentation on Migrating Data.
- Choose your installation method:
This manual covers the 3.2.x series of PuppetDB releases, which is a backward-compatible feature release following the 3.1.x series.
See the release notes for information on all changes.
- The most recent facts from every node
- The most recent catalog for every node
- Optionally, fourteen days (configurable) of event reports for every node
Together, these give you a huge inventory of metadata about every node in your infrastructure and a searchable database of every single resource being managed on any node.
Puppet itself can search a subset of this data using exported resources, which allow nodes to manage resources on other nodes. This is similar to the capabilities of the legacy ActiveRecord
storeconfigs interface, but much, much faster. The remaining data is available through PuppetDB’s query APIs (see navigation sidebar for details).
*nix Server with JDK 1.7+ (Debian) or JDK 1.8+ (RHEL-derived)
Standard Install: RHEL, CentOS, Debian, and Ubuntu
Puppet Labs provides packages and a Puppet module for PuppetDB which simplify setup of its SSL certificates and init scripts. These packages are available for the following operating systems:
- Red Hat Enterprise Linux 6.6+ and 7 (and any derived distro that includes Java 1.8)
- Debian 7 (Wheezy) and 8 (Jessie)
- Ubuntu 12.04 LTS, 14.04 LTS
Custom Install: Any Unix-like OS
If you’re willing to do some manual configuration, PuppetDB can run on any Unix-like OS with JDK 1.7 or higher, including:
- Recent MacOS X versions (using built-in Java 1.8 support)
- Nearly any Linux distribution (using Java 1.8)
- Nearly any *nix system running a recent Oracle-provided 1.8 JDK
Your site’s Puppet masters must be running Puppet 4.0.0 or later. You will need to connect your puppet masters to PuppetDB after installing it. If you wish to use PuppetDB with standalone nodes that are running puppet apply, every node must be running 3.8.1 or later.
Note about Puppet Enterprise
- PuppetDB has been included in Puppet Enterprise since 3.0.0. Users of Puppet Enterprise 2.8 and below can use PuppetDB 1.1 as a separate package, and should visit the PuppetDB 1.1 documentation.
PuppetDB will be a critical component of your Puppet deployment and so should be run on a robust and reliable server.
However, it can do a lot with fairly modest hardware: in benchmarks using real-world catalogs from a customer, a single 2012 laptop (16 GB of RAM, consumer-grade SSD, and quad-core processor) running PuppetDB and PostgreSQL was able to keep up with sustained input from 8,000 simulated Puppet nodes checking in every 30 minutes. Powerful server-grade hardware will perform even better.
The actual requirements will vary wildly depending on your site’s size and characteristics. At smallish sites, you may even be able to run PuppetDB on your puppet master server.
For more on fitting PuppetDB to your site, see “Scaling Recommendations.”
PuppetDB is developed openly, and is released under the Apache 2.0 license. You can get the source — and contribute to it! — at the PuppetDB GitHub repo. Bugs and feature requests are welcome at Puppet Labs’s issue tracker.