Forge Home

Modules

Puppet

Resources

PuppetEcosystemPuppet CommunityUpdates

puppetdb

Puppetdb module
Project URLRSS FeedReport issues

10,858 downloads

10,392 latest version

3.8 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 0.0.2 (latest)
  • 0.0.1
released Oct 16th 2013

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'zooz-puppetdb', '0.0.2'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add zooz-puppetdb
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install zooz-puppetdb --version 0.0.2

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Download
Tags: redhat, puppetdb, hiera, centos

Documentation

zooz/puppetdb — version 0.0.2 Oct 16th 2013

puppetdb

This module installs and configures puppetdb. Currently, puppetdb is only supported to be run on the same host as puppet master.

This module needs to be extended if you want to be able to provision PuppetDB on a separate host than puppet master. I may get this fixed one day.

Parameters

puppetdb class

  • vardir - where to store MQ/DB data. Default: /var/lib/puppetdb.

  • logging_config - use an external log4j config file. Default: /etc/puppetdb/log4j.properties.

  • resource_query_limit - maximum number of results that a resource query may return. Default: 20000.

  • threads - how many command-processing threads to use, defaults to (CPUs / 2). It is set to undef by default, because puppetdb process does calculation itself. It can be specified to whatever number you want if needed.

  • db_subprotocol - what database backend protocol should be used. Valid values: hsqldb or postgresql. Default: hsqldb - embedded db.

  • psql_host - postgresql database host. Default: undef.

  • psql_username - connect to psql database as a specific user. Default: undef.

  • psql_password - connect to psql database with a specific password. Default: undef.

  • gc_interval - how often in minutes to compact the database. Default: 60.

  • node_ttl - auto-deactivate nodes that haven't seen any activity (no new catalogs, facts, etc) in the specified amount of time. Valid values: d - days, h - hours, m - minutes, s - seconds, ms - milliseconds. Default: undef.

  • node_purge_ttl - Automatically delete nodes that have been deactivated for the specified amount of time. This will also delete all facts, catalogs and reports for the node. This ttl may be specified the same way as node-ttl above. If unset, auto-deletion of nodes is disabled. Default: undef.

  • log_slow_statements - number of seconds before any SQL query is considered 'slow'. Default: 10.

  • jvm_heap_size - JVM heap size for PuppetDB. It accepts memory size with a letter suffix - m for megabytes, g for gigabytes, etc. Default: 512m.

Requires

  • Repository added with puppetdb packages
  • CentOS/RHEL/Fedora distribution

Examples

Below example shows how to use this module with hiera + yaml backend.

---
classes:
  - puppetdb

puppetdb::threads:       '4'
puppetdb::jvm_heap_size: '1024m'

Authors