Difference between revisions of "Puppet"

From ArchWiki
Jump to: navigation, search
(Puppet 3.2.0rc1)
(Style clean up. See Help:Style.)
(19 intermediate revisions by 2 users not shown)
Line 4: Line 4:
 
:''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 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.''
  
= Installation =
+
== Installation ==
  
Puppet packages are available in AUR. Install either puppet or puppet-git. The maintainer of the puppet AUR packages is not interested in shipping patches to minimize work as well as avoid confusion as to where bugs should go. So I will collect my patches here.
+
Puppet packages are available in [[AUR]]. Install either {{AUR|puppet}} or {{AUR|puppet-git}}.
  
= Configuration =
+
== Configuration ==
  
Puppet will look for your configuration in {{ic|<nowiki>/etc/puppet/manifests/site.pp</nowiki>}}.
+
Puppet's main configuration file is puppet.conf which is located at
 +
{{ic|<nowiki>/etc/puppet/puppet.conf</nowiki>}}.
 +
You have 3 options to place settings depending if it is a master/agent<br>
 +
  [main]
 +
  [agent]
 +
  [master]
 +
 
 +
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 {{ic|<nowiki>/etc/puppet/manifests/site.pp</nowiki>}}.
 +
 
 +
After starting puppet by daemon/cron/standalone, it will generate
 +
certificates in {{ic|<nowiki>/etc/puppet/ssl/</nowiki>}} directory.
 +
And you need to accept this certificaten the puppet master with:
 +
{{ic|<nowiki>sudo puppet cert sign <name></nowiki>}}.
  
 
== Facter ==
 
== Facter ==
  
Facter is a package that gathers facts about the system it runs on. Use with {{ic|<nowiki>puppet facts find facter</nowiki>}}.
+
Facter is a companion program of puppet that gathers facts about the system it runs on.<br>
 +
commands:
 +
# puppet facts find facter
 +
# facter -p
  
 +
=== Installation ===
 +
Install it from aur {{AUR|ruby-facter}}.
 
Facter requires both {{ic|<nowiki>ifconfig</nowiki>}} as well as {{ic|<nowiki>ip</nowiki>}} to gather network related facts.
 
Facter requires both {{ic|<nowiki>ifconfig</nowiki>}} as well as {{ic|<nowiki>ip</nowiki>}} to gather network related facts.
  
=== Ruby-Facter 1.7.0 ===
+
With facter 1.7.0 the new {{ic|ifconfig}} in arch will give proper output to IP adresses, but netmask/mtu are still a problem.
 
+
With facter 1.7.0 the new {{ic|<nowiki>ifconfig</nowiki>}} in arch will give proper output
+
to IP adresses, <br>but netmask/mtu are still a problem.
+
  
 
Netmask has been adressed on github version of facter.
 
Netmask has been adressed on github version of facter.
  
==Packages==
+
== puppet resources ==
 +
===Packages===
  
"Pacman" is supported by puppet. Installing packages works out of the box with puppet 3.1.0 and the git packages.
+
"Pacman" is supported by puppet. Installing packages works out of the box since puppet 3.1.0.
  
==Services==
+
===Services===
  
===Puppet 3.2.0rc1===
+
Since puppet 3.2.1 systemd on archlinux is fully supported.<br>
 +
The systemd provider in Puppet today only uses two commands for the service enable state:<br>
 +
  systemctl is-enabled <unit>, checking return code for the current enable state<br>
 +
  systemctl enable/disable <unit> to change it.
  
Has been released and has been uploaded to aur. The diff below needs to be changed accordingly.
+
Otherwise service running will use:
 +
  # systemctl start/stop/restart <unit>
  
Puppet has trouble with systemd on arch linux. This diff fixes it:
+
Using the full unit name unit.service is supported.
--- puppet-3.1.0-orig/lib/puppet/provider/service/systemd.rb    2013-02-25 08:49:29.000000000 +0100
+
+++ puppet-3.1.0/lib/puppet/provider/service/systemd.rb 2013-02-26 16:59:36.828276309 +0100
+
@@ -3,9 +3,10 @@
+
  Puppet::Type.type(:service).provide :systemd, :parent => :base do
+
    desc "Manages `systemd` services using `/bin/systemctl`."
+
 
+
-  commands :systemctl => "/bin/systemctl"
+
+  commands :systemctl => "/usr/bin/systemctl"
+
 
+
    #defaultfor :osfamily => [:redhat, :suse]
+
+  defaultfor :osfamily => [:archlinux]
+
 
+
    def self.instances
+
      i = []
+
  
Apply in {{ic|<nowiki>/usr/lib/ruby/gems/1.9.1/gems</nowiki>}}.
+
== extra/patches ==
 +
===Puppet 3.2.1===
  
 
If you want to enable the "storeconfig" option in /etc/puppet/puppet.conf you will also need this patch:
 
If you want to enable the "storeconfig" option in /etc/puppet/puppet.conf you will also need this patch:
Line 74: Line 86:
 
Apply in the same place.
 
Apply in the same place.
  
= See also =
+
Before you apply above patch read this:[http://projects.puppetlabs.com/projects/1/wiki/using_stored_configuration using_stored_configuration]
 +
 
 +
==puppetdb ==
 +
PuppetDB is the fast, scalable, and reliable data warehouse for Puppet.<br>
 +
It caches data generated by Puppet, and gives you advanced features at awesome speed with a powerful API.<br>
 +
Puppetdb is in aur install {{AUR|puppetdb}} and {{AUR|puppetdb-terminus}} <br>
 +
[More information: https://github.com/puppetlabs/puppetdb]
 +
 
 +
== See also ==
 
* [[Puppet Dashboard]] - Software based on or using puppet in this wiki.
 
* [[Puppet Dashboard]] - Software based on or using puppet in this wiki.

Revision as of 07:45, 24 August 2013

Tango-document-new.pngThis article is a stub.Tango-document-new.png

Notes: This wiki entry is a work-in-progress. (Discuss in Talk:Puppet#)

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.

Installation

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

Configuration

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

 [main]
 [agent]
 [master]

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

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

# puppet facts find facter
# facter -p

Installation

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

Packages

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

Services

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.

extra/patches

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 @@
   end
 
   def [](param)
-    super || parameter(param)
+    if param == 'id'
+      super
+    else
+      super || parameter(param)
+    end
   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

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