From ArchWiki
Revision as of 07:45, 24 August 2013 by Fengchao (talk | contribs) (Style clean up. See Help:Style.)
Jump to navigation Jump to search

From Puppet web site:

Puppet is IT automation software that helps system administrators manage infrastructure throughout its lifecycle, from provisioning and configuration to patch management and compliance. Using Puppet, you can easily automate repetitive tasks, quickly deploy critical applications, and proactively manage change, scaling from 10s of servers to 1000s, on-premise or in the cloud.


Puppet packages are available in AUR. Install either puppetAUR or puppet-gitAUR.


Puppet's main configuration file is puppet.conf which is located at /etc/puppet/puppet.conf. You have 3 options to place settings depending if it is a master/agent


Bare minimum of settings are:

  • server: The hostname of the puppet server. Default = puppet
  • report: Most users should set this to true.
  • pluginsync: Most users should set this to true.
  • certname: The certified name of the machine (unique identifier) default = fqdn

Puppet will look for node configuration in /etc/puppet/manifests/site.pp.

After starting puppet by daemon/cron/standalone, it will generate certificates in /etc/puppet/ssl/ directory. And you need to accept this certificaten the puppet master with: sudo puppet cert sign <name>.


Facter is a companion program of puppet that gathers facts about the system it runs on.

# puppet facts find facter
# facter -p


Install it from aur ruby-facterAUR. Facter requires both ifconfig as well as ip to gather network related facts.

With facter 1.7.0 the new ifconfig in arch will give proper output to IP adresses, but netmask/mtu are still a problem.

Netmask has been adressed on github version of facter.

puppet resources


"Pacman" is supported by puppet. Installing packages works out of the box since puppet 3.1.0.


Since puppet 3.2.1 systemd on archlinux is fully supported.
The systemd provider in Puppet today only uses two commands for the service enable state:

 systemctl is-enabled <unit>, checking return code for the current enable state
systemctl enable/disable <unit> to change it.

Otherwise service running will use:

 # systemctl start/stop/restart <unit>

Using the full unit name unit.service is supported.


Puppet 3.2.1

If you want to enable the "storeconfig" option in /etc/puppet/puppet.conf you will also need this patch:

diff -urN puppet-3.1.1-orig/lib/puppet/rails/resource.rb puppet-3.1.1/lib/puppet/rails/resource.rb
--- puppet-3.1.1-orig/lib/puppet/rails/resource.rb      2013-03-13 20:53:21.766846140 +0100
+++ puppet-3.1.1/lib/puppet/rails/resource.rb   2013-03-13 21:01:07.337490296 +0100
@@ -84,7 +86,11 @@
   def [](param)
-    super || parameter(param)
+    if param == 'id'
+      super
+    else
+      super || parameter(param)
+    end
   # Make sure this resource is equivalent to the provided Parser resource.

Apply in the same place.

Before you apply above patch read this:using_stored_configuration


PuppetDB is the fast, scalable, and reliable data warehouse for Puppet.
It caches data generated by Puppet, and gives you advanced features at awesome speed with a powerful API.
Puppetdb is in aur install puppetdbAUR and puppetdb-terminusAUR
[More information: https://github.com/puppetlabs/puppetdb]

See also