puppet 3.0.2 → 3.1.0.rc1

data/README_HIERA.md

@@ -1,148 +0,0 @@
-What?
-=====
-
-A data backend for Hiera that can query the internal Puppet
-scope for data.  The data structure and approach is heavily
-based on work by Nigel Kersten but made more configurable and
-with full hierarchy.
-
-It also includes a Puppet function that works like extlookup()
-but uses the Hiera backends.
-
-Usage?
-======
-
-Hiera supports the concept of chaining backends together in order,
-using this we can create a very solid module author/module user
-experience.
-
-Module Author
--------------
-
-A module author wants to create a configurable module that has sane
-defaults but want to retain the ability for users to configure it.
-
-We'll use a simple NTP config class as an example.
-
-<pre>
-class ntp::config($ntpservers = hiera("ntpservers")) {
-   file{"/etc/ntp.conf":
-       content => template("ntp.conf.erb")
-   }
-}
-</pre>
-
-We create a class that takes as parameters a list of NTP servers.
-
-The module author wants to create a works-out-of-the-box experience
-so creates a data class for the NTP module:
-
-<pre>
-class ntp::data {
-   $ntpservers = ["1.pool.ntp.org", "2.pool.ntp.org"]
-}
-</pre>
-
-Together this creates a default sane setup.
-
-Module User
------------
-
-The module user has a complex multi data center setup, he wants to use
-the NTP module from the forge and configure it for his needs.
-
-The user creates a set of default data for his organization, he can do
-this in data files or in Puppet.  We'll show a Puppet example.
-
-<pre>
-class data::common {
-   $ntpservers = ["ntp1.example.com", "ntp2.example.com"]
-}
-</pre>
-
-Being part of the actual code this data is subject to strict change
-control.  This is needed as its data that can potentially affect all
-machines in all locations.
-
-The user has a fact called _location_ that contains, for example, a name
-of the data center.
-
-He decides to create JSON based data for the data centers, being just data
-that applies to one data center this data is not subject to as strict
-change controls and so does not live with the code:
-
-He creates _/var/lib/hiera/dc1.json_ with the following:
-
-<pre>
-{"ntpservers" : ["ntp1.dc1.example.com", "ntp2.dc1.example.com"]}
-</pre>
-
-Machines in dc1 will now use specific NTP servers while all the rest will
-use the data in _data::common_
-
-The module user can now just declare the class on his nodes:
-
-<pre>
-node "web1" {
-   include ntp::config
-}
-</pre>
-
-For true one-off changes, the user can use the full paramterized class approach
-that will completely disable the Hiera handling of this data item.  He could
-also use an ENC to supply this data.
-
-<pre>
-node "web2" {
-   class{"ntp::config": ntpservers => ["another.example.com"]}
-}
-</pre>
-
-This behavior is thanks to Hiera's ability to search through multiple backends
-for data picking the first match.  We can have the JSON searched before the internal
-Puppet data.
-
-To achieve this setup the module user needs to configure Hiera in _/etc/puppet/hiera.yaml_:
-
-<pre>
----
-:backends:
-  - json
-  - puppet
-
-:hierarchy:
-  - "%{location}"
-  - common
-
-:json:
-  :datadir: /var/lib/hiera
-
-:puppet:
-	:datasource: data
-</pre>
-
-Converting from extlookup?
-==========================
-
-A simple converter is included called _extlookup2hiera_ and it can convert from CSV to JSON or YAML:
-
-<pre>
-$ extlookup2hiera --in common.csv --out common.json --json
-</pre>
-
-Installation?
-=============
-
-It's not 100% ready for prime time, shortly a simple _gem install hiera-puppet_ on your master will do it.
-
-For the moment the Gem install will place the Puppet Parser Function where Puppet cannot find it, you should
-copy it out and distribute it to your master using Pluginsync or something similar
-
-License
-=======
-
-See LICENSE file.
-
-Support
-=======
-Please log tickets and issues at our [Projects site](http://projects.puppetlabs.com)

data/conf/epm.list

@@ -1,8 +0,0 @@
-%product Puppet
-%copyright 2004-2005 by Reductive Labs, All Rights Reserved
-%vendor Reductive Labs
-%license COPYING
-%readme README
-%description System Automation and Configuration Management Software
-%version 0.15.0
-%requires facter 1.1

data/conf/namespaceauth.conf

@@ -1,20 +0,0 @@
-# This is an example namespaceauth.conf file,
-# which you'll need if you want to start a client
-# in --listen mode.
-[fileserver]
-    allow *.domain.com
-
-[puppetmaster]
-    allow *.domain.com
-
-[puppetrunner]
-    allow culain.domain.com
-
-[puppetbucket]
-    allow *.domain.com
-
-[puppetreports]
-    allow *.domain.com
-
-[resource]
-    allow server.domain.com

data/conf/puppet-queue.conf

@@ -1,10 +0,0 @@
-:daemon: true
-:working_dir: /tmp/stompserver
-:storage: .queue
-:queue: file
-:auth: false
-:debug: false
-:group:
-:user:
-:host: 127.0.0.1
-:port: 61613

data/examples/allatonce

@@ -1,13 +0,0 @@
-# $Id$
-
-define thingie {
-    file { "/tmp/classtest": ensure => file, mode => 755 }
-    #testing {}
-}
-
-class testing {
-    thingie { "componentname": }
-}
-
-#component {}
-testing { "testingname": }

data/examples/assignments

@@ -1,11 +0,0 @@
-# $Id$
-
-$goodness = sunos
-
-$subvariable = $goodness
-
-$yayness = "this is a string of text"
-
-#$sleeper = service { sleeper:
-#    running => "1"
-#}

data/examples/components

@@ -1,73 +0,0 @@
-# $Id$
-
-# i still have no 'require'-like functionality, and i should also
-# have 'recommend'-like functionality...
-define apache(php,docroot,user,group) {
-    package { apache:
-        version => "2.0.53"
-    }
-    service { apache:
-        running => true
-    }
-
-
-    # this definitely won't parse
-    #if $php == "true" {
-    #    # this needs to do two things:
-    #    # - mark a dependency
-    #    # - cause this apache component to receive refresh events generated by php
-    #    #require("php")
-    #    $var = value
-    #}
-
-    #file { "../examples/root/etc/configfile":
-    #    owner => $user
-    #}
-}
-
-define sudo() {
-    package { sudo:
-        version => "1.6.8p7"
-    }
-    file { "/etc/sudoers":
-        owner => root,
-        group => root,
-        mode => "440"
-    }
-}
-
-define ssh {
-    package { ssh:
-        version => "3.4.4.4"
-    }
-    service { "sshd":
-        running => true
-    }
-}
-
-define sleeper(path,mode) {
-    Service {
-        path => "../examples/root/etc/init.d"
-    }
-
-    service { sleeper:
-        running => true,
-        path => "../examples/root/etc/init.d"
-    }
-    file { $path:
-        mode => $mode
-    }
-    $files = ["/tmp/testness","/tmp/funtest"]
-    file { $files:
-        ensure => file
-    }
-}
-
-#apache { "test":
-#    php => false,
-#    docroot => "/export/html",
-#    user => "www-data",
-#    group => "www-data"
-#}
-
-#ssh { "yucko":}

data/examples/etc/init.d/sleeper

@@ -1,70 +0,0 @@
-#!/bin/bash
-
-script=$0
-path=`echo $script | sed 's/etc..*/bin/'`
-
-PATH=$PATH:$path
-
-ps=`facter ps`
-
-if [ -z "$ps" ]; then
-    ps="ps -ef"
-fi
-
-function start
-{
-    cd $path
-    ./sleeper
-}
-
-function stop
-{
-    #if [ -n `which pgrep` ]; then
-    #    pid=`pgrep sleeper`
-    #else
-        pid=`$ps | grep -v grep | grep sleeper | grep ruby | awk '{print $2}'`
-    #fi
-    if [ -n "$pid" ]; then
-        kill $pid
-    fi
-}
-
-function restart
-{
-    stop
-    start
-}
-
-function status
-{
-    #if [ -n `which pgrep` ]; then
-    #    cmd="pgrep sleeper"
-    #else
-        #cmd="$ps | grep -v grep | grep sleeper | grep ruby | awk '{print $2}'"
-    #fi
-    #$cmd
-    $ps | grep -v grep | grep sleeper | grep ruby
-}
-
-case "$1" in
-    start)
-        start
-    ;;
-    stop)
-        stop
-    ;;
-    restart)
-        stop; start
-    ;;
-    status)
-        output=`status`
-        #status
-        exit $?
-    ;;
-    *)
-        echo "Usage: $N {start|stop|restart|force-reload}" >&2
-        exit 1
-    ;;
-esac
-
-exit 0

data/examples/etc/puppet/fileserver.conf

@@ -1,13 +0,0 @@
-# $Id$
-
-[dist]
-    path /dist
-    allow *.puppetlabs.com
-
-[plugins]
-    path /var/lib/puppet/plugins
-    allow *.puppetlabs.com
-
-[facts]
-    path /var/lib/puppet/facts
-    allow *.puppetlabs.com

data/examples/etc/puppet/namespaceauth.conf

@@ -1,20 +0,0 @@
-# This file is only necessary if your clients listen.
-# Note that it affects all puppet daemons, including puppetmasterd,
-# which is why puppetmaster is in there.
-[fileserver]
-    allow *.madstop.com
-
-[puppetmaster]
-    allow *.madstop.com
-
-[pelementserver]
-    allow puppet.madstop.com
-
-[puppetrunner]
-    allow culain.madstop.com
-
-[puppetbucket]
-    allow *.madstop.com
-
-[puppetreports]
-    allow *.madstop.com

data/examples/etc/puppet/puppet.conf

@@ -1,10 +0,0 @@
-[puppetd]
-report = true
-factsync = true
-pluginsync = true
-
-[puppetmasterd]
-reports = store,rrdgraph,tagmail,log
-node_terminus = ldap
-ldapserver = culain.madstop.com
-ldapbase = dc=madstop,dc=com

data/examples/etc/puppet/tagmail.conf

@@ -1 +0,0 @@
-all: user@domain.com

data/examples/execs

@@ -1,16 +0,0 @@
-$path = "/usr/bin:/bin"
-
-exec { "mkdir -p /tmp/fakedir":
-    path => $path
-}
-
-exec { "rm -rf /tmp/fakedir":
-    path => $path
-}
-
-exec { "touch /this/directory/does/not/exist":
-    path => $path,
-    returns => 1
-}
-
-

data/examples/file.bl

@@ -1,11 +0,0 @@
-# $Id$
-
-file {
-    "/tmp/atest": ensure => file, mode => 755;
-    "/tmp/btest": ensure => file, mode => 755
-}
-
-file {
-    "/tmp/ctest": ensure => file;
-    "/tmp/dtest": ensure => file;
-}