This module implements command line tools and Puppet functions that can be used to query puppetdb. There's also a hiera backend that can be used to return query results from puppetdb.
The query format accepts resource references in the form:
Type[Name]{attribute1=foo and attribute2=bar}
Each of the three parts are optional. It will only match non exported resources by default, to match exported resources add @@ in front.
Facts can be matched using the operators =, !=, >, < and ~ (regexp match). > and < only work on numbers, ~ only works on strings.
Any expression can be combined using "not", "and" or "or", in that precedence order. To change precedence you can use parenthesis.
Alphanumeric strings don't need to be quoted, but can be quoted using double quotes with the same escaping rules as JSON. Numbers are interpreted as numbers and true/false as boolean values, to use them as strings instead simply quote them.
Ensure that the lib directory is in Ruby's LOADPATH.
$ export RUBYLIB=puppet-puppetdbquery/lib:$RUBYLIB
PuppetDB terminus is required for the Puppet functions, but not the face.
To get a list of the supported subcommands for the query face, run:
$ puppet help query
You can run puppet help on the returned subcommands
$ puppet help query nodes
$ puppet help query facts
Each of the faces uses the following query syntax to return all objects found on a subset of nodes:
# get all nodes that contain the apache package and are in france, or all nodes in the us
$ puppet query nodes '(Package[httpd] and country=fr) or country=us'
Each of the individual faces returns a different data format:
nodes - a list of nodes identified by a name
$ puppet query nodes '(Package["mysql-server"] and architecture=amd64)'
["db_node_1", "db_node2"]
facts - a hash of facts per node
$ puppet query facts '(Package["mysql-server"] and architecture=amd64)'
db_node_1 {"facterversion":"1.6.9","hostname":"controller",...........}
db_node_2 {"facterversion":"1.6.9","hostname":"controller",...........}
events - a list of events on the matched nodes
$ puppet query events '(Package["mysql-server"] and architecture=amd64)' --since='1 hour ago' --until=now --status=success
host.example.com: 2013-06-10T10:58:37.000Z: File[/foo/bar]/content ({md5}5711edf5f5c50bd7845465471d8d39f0 -> {md5}e485e731570b8370f19a2a40489cc24b): content changed '{md5}5711edf5f5c50bd7845465471d8d39f0' to '{md5}e485e731570b8370f19a2a40489cc24b'
faces can be called from the ruby in exactly they same way they are called from the command line:
$ irb> require 'puppet/face'
irb> Puppet::Face[:query, :current].nodes('(Package["mysql-server"] and architecture=amd64)')
There's corresponding functions to query PuppetDB directly from Puppet manifests.
Accepts two arguments, a query used to discover nodes, and a optional fact that should be returned.
Returns an array of certnames or fact values if a fact is specified.
$hosts = query_nodes('manufacturer~"Dell.*" and processorcount=24 and Class[Apache]')
$hostips = query_nodes('manufacturer~"Dell.*" and processorcount=24 and Class[Apache]', ipaddress)
Similar to query_nodes but takes two arguments, the first is a query used to discover nodes, the second is a list of facts to return for those nodes.
Returns a nested hash where the keys are the certnames of the nodes, each containing a hash with facts and fact values.
query_facts('Class[Apache]{port=443}', ['osfamily', 'ipaddress'])
Example return value in JSON format:
{ "foo.example.com": { "ipaddress": "192.168.0.2", "osfamily": "Redhat" }, "bar.example.com": { "ipaddress": "192.168.0.3", "osfamily": "Debian" } }
The hiera backend can be used to return an array with results from a puppetdb query. It requires another hiera backend to be active at the same time, and that will be used to define the actual puppetdb query to be used. It does not matter which backend that is, there can even be several of them. To enable add the backend puppetdbto the backends list in hiera.yaml.
So instead of writing something like this in for example your hiera-data/common.yaml:
ntp::servers:
- 'ntp1.example.com'
- 'ntp2.example.com'
You can now instead write:
ntp::servers::_nodequery: 'Class[Ntp::Server]'
It will then find all nodes with the class ntp::server and return an array containing their certname. If you instead want to return the value of a fact, for example the ipaddress, the nodequery can be a tuple, like:
ntp::servers::_nodequery: ['Class[Ntp::Server]', 'ipaddress']
or a hash:
ntp::servers::_nodequery:
query: 'Class[Ntp::Server]'
fact: 'ipaddress'
When returning facts only nodes that actually have the fact are returned, even if more nodes would in fact match the query itself.
This module also contains some older deprecated functions that use the raw version 1 PuppetDB API. They require the json ruby gem and the puppetdb-terminus.
Only queries over HTTPS are supported atm.
The first argument is the resource query. Second argument is optional but allows you to specify the item you want from the returned hash.
It automatically excludes deactivated hosts.
Returns an array of hashes or array of strings if second argument is provided.
# Return an array of hashes describing all files that are owned by root on active hosts.
$ret = pdbresourcequery(
['and',
['=','type','File'],
['=',['parameter','owner'],'root']])
# Return an array of host names having those resources
$ret = pdbresourcequery(
['and',
['=',['node','active'],true],
['=','type','File'],
['=',['parameter','owner'],'root']], 'certname')
Works exactly like pdbresourcequery but also returns deactivated hosts.
The first argument is the node query. Second argument is optional but allows you to specify a resource query that the nodes returned also have to match.
It automatically excludes deactivated hosts.
Returns a array of strings with the certname of the nodes (fqdn by default).
# Return an array of active nodes with an uptime more than 30 days
$ret = pdbnodequery(['>',['fact','uptime_days'],30])
# Return an array of active nodes with an uptime more than 30 days and
# having the class 'apache'
$ret = pdbnodequery(
['>',['fact','uptime_days'],30],
['and',
['=','type','Class'],
['=','title','Apache']])
Works exactly like pdbnodequery but also returns deactivated hosts.
The first argument is the node to get facts for. It can be either a single node or an array of nodes. If it is an array the return value of the function will also be an array. Second argument is optional, if specified only return that specific fact.
# Get hash of facts for foo.example.com
pdbfactquery('foo.example.com')
# Get the uptime fact for foo.example.com
pdbfactquery('foo.example.com', 'uptime')
# Get the uptime fact for foo.example.com and bar.example.com
pdbfactquery(['foo.example.com', 'bar.example.com'], 'uptime')
The first argument is the node to get the status for. Second argument is optional, if specified only return that specific bit of status, one of 'name', 'deactivated', 'catalog_timestamp' and 'facts_timestamp'.
Returns an array of hashes or a array of strings if second argument is supplied.
# Get status for foo.example.com
pdbstatusquery('foo.example.com')
# Get catalog_timestamp for foo.example.com
pdbstatusquery('foo.example.com', 'catalog_timestamp')
This is the generic query function that the others make use of, you probably don't have to use it and can use one of the specific functions listed above instead.
The first argument is the URL path that should be queried, for example 'nodes' or 'status/nodes/'. The second argument if supplied if the query parameter, if it is a string it is assumed to be JSON formatted and sent as is, anything else is converted to JSON and then sent.
# Get list of all active nodes
$ret = pdbquery('nodes', ['=', ['node', 'active'], true ])
# Query status of current node
$ret2 = pdbquery("status/nodes/${settings::certname}")
See http://docs.puppetlabs.com/puppetdb for more info and examples about the PuppetDB API.