1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
|
Puppet-Module for configuring Puppet itself, both the master and the clients
============================================================================
Use a seperate local module called "site-puppet", where you place your customized
files, under:
site-puppet/files/master/fileserver.conf
site-puppet/files/master/puppet.conf
those files in this module are just examples.
Depends on Modules
------------------
- bc
Usage
=====
The module currently looks for values on different variables to adjust
configuration of the master.
Mode:
-----
If you want to run the puppetmaster in a non-webrick based
mode, you can set $puppetmaster_mode either to:
* passenger, run puppetmaster as a passenger application
* cluster, run puppetmaster as a mongrel based cluster
In both cases you have to setup the appropriate frontends
(apache vhost configuration/nginx vhost configuration) on
your own.
Reports cleanup:
---------------
By default we clean up reports older than 30 days. If you want to change
that, you can set $puppetmaster_cleanup_reports to one of the following
values:
* 'X', where X is the amount of days you want to keep reports for
* false, to disable reports cleanup
Check last run:
---------------
We can check on the last run state of certain clients, to check whether
they still check in. You can do that by setting the following variables:
$puppetmaster_checklastrun
* any cron time: '20 10,22 * * *' to run the script at a certain time
by cron. Default: 40 10,22 * * *
* false: to disable check for last run
Example:
--------
in your site.pp, i.e. :
$puppet_crontime = "0,12 * * * *"
include puppet::cron
$puppetmaster_mode = 'passenger'
include puppet::puppetmaster
$puppet_storeconfig_password="..."
include puppet::puppetmaster::storeconfigs
...tbc...
|
