1() ()
2
6 -
7
11 Trigger a puppetd run on a set of hosts.
12
16 puppetrun [-a|--all] [-c|--class <class>] [-d|--debug] [-f|--fore‐
17 ground]
18 [-h|--help] [--host <host>] [--no-fqdn] [--ignoreschedules]
19 [-t|--tag <tag>] [--test]
20
25 This script can be used to connect to a set of machines running +pup‐
26 petd+ and trigger them to run their configurations. The most common
27 usage would be to specify a class of hosts and a set of tags, and +pup‐
28 petrun+ would look up in LDAP all of the hosts matching that class,
29 then connect to each host and trigger a run of all of the objects with
30 the specified tags.
31 If you are not storing your host configurations in LDAP, you can spec‐
33 ify hosts manually.
34 You will most likely have to run +puppetrun+ as root to get access to
36 the SSL certificates.
37 +puppetrun+ reads +puppetmaster+´s configuration file, so that it can
39 copy things like LDAP settings.
40
44 +puppetrun+ is useless unless +puppetd+ is listening. See its documen‐
45 tation for more information, but the gist is that you must enable +lis‐
46 ten+ on the +puppetd+ daemon, either using +--listen+ on the command
47 line or adding ´listen: true´ in its config file. In addition, you need
48 to set the daemons up to specifically allow connections by creating the
49 +namespaceauth+ file, normally at ´/etc/puppet/namespaceauth.conf´.
50 This file specifies who has access to each namespace; if you create the
51 file you must add every namespace you want any Puppet daemon to allow
52 -- it is currently global to all Puppet daemons.
53 An example file looks like this:
55 [fileserver]
58 allow *.madstop.com
59 [puppetmaster]
61 allow *.madstop.com
62 [puppetrunner]
64 allow culain.madstop.com
65 This is what you would install on your Puppet master; non-master hosts
66 could leave off the ´fileserver´ and ´puppetmaster´ namespaces.
67 Expect more documentation on this eventually.
69
73 Note that any configuration parameter that´s valid in the configuration
74 file is also a valid long argument. For example, ´ssldir´ is a valid
75 configuration parameter, so you can specify ´--ssldir <directory>´ as
76 an argument.
77 See the configuration file documentation at http://reductive‐
79 labs.com/projects/puppet/reference/configref.html for the full list of
80 acceptable parameters. A commented list of all configuration options
81 can also be generated by running puppetmasterdd with ´--genconfig´.
82 all: Connect to all available hosts. Requires LDAP support
86 at this point.
87 class: Specify a class of machines to which to connect. This
91 only works if you have LDAP configured, at the moment.
92 debug: Enable full debugging.
94 foreground: Run each configuration in the foreground; that is, when
98 connecting to a host, do not return until the host has finished
99 its run. The default is false.
100 help: Print this help message
102 host: A specific host to which to connect. This flag can be
106 specified more than once.
107 ignoreschedules: Whether the client should ignore schedules when run‐
111 ning
112 its configuration. This can be used to force the client to per‐
113 form work it would not normally perform so soon. The default is
114 false.
115 parallel: How parallel to make the connections. Parallelization
119 is provided by forking for each client to which to connect. The
120 default is 1, meaning serial execution.
121 tag: Specify a tag for selecting the objects to apply. Does
125 not work with the --test option.
126 test: Print the hosts you would connect to but do not
130 actually connect. This option requires LDAP support at this
131 point.
132
136 sudo puppetrun -p 10 --host host1 --host host2 -t remotefile -t web‐
137 server
138
143 Luke Kanies
144
148 Copyright (c) 2005 Reductive Labs, LLC Licensed under the GNU Public
149 License
150 ()