On Sun, Aug 19, 2012 at 10:31 AM, treydock treyd...@gmail.com wrote:
Ive struggled with the same problem of distributing variables and other
generated data amongst hosts.
For external resources Ive found a great use in configuring a BackupPC
server. Each node builds their backup
Ive struggled with the same problem of distributing variables and other
generated data amongst hosts.
For external resources Ive found a great use in configuring a BackupPC server.
Each node builds their backup configuration file with tag
'backuppc_server_conf' and the server retrieves all
On Tuesday, August 14, 2012 2:27:05 PM UTC-5, Sam wrote:
what is the right way to handle this?
On Tuesday, May 12, 2009 7:51:31 AM UTC+1, stever...@gmail.com wrote:
So I want to use facts from one host in the configuration of other
hosts.
Trivial example: setting restrict lines in
On Wednesday, August 15, 2012 8:31:52 AM UTC-5, jcbollinger wrote:
The original and main idea of exported resources is for the node that
knows what a resource is actually supposed to look like to declare the node
on behalf of the nodes that need it
I meant declare the *resource* on
what is the right way to handle this?
On Tuesday, May 12, 2009 7:51:31 AM UTC+1, stever...@gmail.com wrote:
So I want to use facts from one host in the configuration of other
hosts.
Trivial example: setting restrict lines in ntp.conf to allow a
monitoring host to query ntpd on remote
Hello,
Am 12.05.2009 um 08:51 schrieb steverfran...@gmail.com:
Or do I have to copy the IP address of the monitor host to each
machine, via an exported resource file, and then process it locally in
an exec script to build the correct ntp.conf?
That doesn't seem very puppet-ish...
No, but I
So how about a slightly less trivial example, such as configuring a
haproxy config based on the addresses of 2 web servers?
THe puppetmaster knows the addresses of the 2 web servers; it knows
the proxy is a proxy, and the form of the config file, but I cant see
how to put all that information
