Tore <[email protected]> writes:
> Thanks again for the answers. I've haven't got to much time to play with
> puppet, but I always seems to forget that puppet compiles the code at the
> master, and sends this code to the nodes. The only thing that is transferred
> from the nodes regarding information, is facter information. Hence the
> variable ($ifconfig = generate("/usr/sbin/ ifconfig", "eth0") will be equal
> on all nodes when they get the compiled configuration.
Yes, it would, because it would run ifconfig on master on each node.
> The only simple way I can think of is creating a manifest which uses curl to
> POST a file to a HTTP server (or some other protocol). It can be quite time
> consuming to compare 30 httpd.conf just to verify that they are equal (they
> should be, but you never know without checking it) before managing them with
> puppet.
*nod*
For what it is worth, I would suggest that you set up a suite of ad-hoc change
tools to work alongside puppet (or, in fact, alongside any tool that works
like puppet.)
For those ad-hoc tools the ability to run a shell command, as an arbitrary
user, and to transfer files to and from the systems is invaluable.
It is also ideal if you can easily say "only these systems" to the tool.
Then you can use that to drag down the httpd.conf on all the machines, or
sha1sum them and find what is identical, or...
You don't want to use ad-hoc change tools often, but when you need them they
are invaluable. This is *especially* true when you have a one-shot job like
"compare these files before we take 'em over" to do.
Daniel
--
✣ Daniel Pittman ✉ [email protected] ☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
