Directories: The Cache Directory (vardir)
Included in Puppet Enterprise 2015.3. A newer version is available; see the version menu above for details.
Puppet’s cache directory, sometimes called
vardir, contains dynamic and/or growing data that Puppet creates automatically in the course of its normal operations. Some of this data can be mined for interesting analysis, or to integrate other tools with Puppet; other parts are just infrastructure and should be ignored by most or all users.
Puppet agent/apply and Puppet Server use different cache directories.
Puppet Server’s cache directory defaults to:
The cache directory for Puppet agent and Puppet apply can be found at one of the following locations:
- *nix Systems:
- non-root users:
When Puppet is running as either root, a Windows user with administrator privileges, or the
puppet user, it will use a system-wide cache directory. When running as a non-root user, it will use a cache directory in that user’s home directory.
The system cache directory is what you usually want to use, since you will usually run Puppet’s commands and services as root or
puppet. (Note that admin commands like
puppet cert must be run with
sudo to use the same directories as Puppet agent or Puppet master.)
Note: When Puppet master is running as a Rack application, the
config.rufile must explicitly set
--vardirto the system cache directory. The example
config.rufile provided with the Puppet source does this.
Puppet’s cache directory can be specified on the command line with the
--vardir option, but it can’t be set via puppet.conf. If
--vardir isn’t specified when a Puppet application is started, it will always use the default cache directory location.
Puppet Server uses the
jruby-puppet.master-var-dir setting in puppetserver.conf to configure its cache directory.
Since the value of the vardir is discovered before other settings, you can safely reference it (with the
$vardir variable) in the value of any other setting in puppet.conf or on the command line:
[main] ssldir = $vardir/ssl
If you need to set nonstandard values for some settings, this allows you to avoid absolute paths and keep your Puppet-related files together.
The vardir contains several directories. Most of these subdirectories contain a variable amount of automatically generated data; some of them contain notable individual files. Some directories are used only by agent or master processes.
The default layout of the vardir is as follows. Most of the files and directories can have their locations changed with settings in puppet.conf. The link for each item goes to its description in the configuration reference.
libdir) (also plugindest) — Puppet uses this as a cache for plugins (custom facts, types and providers, functions) synced from a Puppet master. It shouldn’t be directly modified by the user. It can be safely deleted, and the plugins will be restored on the next Puppet run.
reportdir) — When the
storereport is enabled, a Puppet master will store all reports received from agents as YAML files in this directory. These can be easily mined for analysis by an out-of-band process.
classfile) — This file is a favorite for external integration. It lists all of the classes assigned to this agent node.
graphdir) — Agent nodes write a set of .dot graph files to this directory when graphing is enabled. These graphs can be used to diagnose problems with catalog application, as well as to visualize the configuration catalog.
templatedir) — This directory generally shouldn’t be used; templates should be stored in modules.