> 2 - Can I say "install this shellscript and run it once"? How?
>
> 2a - Is there an ISConf-like facility that says "run it until it
> succeeds once"? [ Happy to use Makefiles, but if there's a
> Puppet-supported elegant way of doing it... ]
If the code of the shell script can be minimized to use as much as of
Puppet's existing resources, that would be a good way to go about
things. Of course, you can execute the shell scripts, and define the
conditions that you mentioned. Have a look at the exec resource type
in puppet for such things.
> 3 - Can I hook up a trigger so when a new conffile for a service is
> installed the service is restarted? IE: I provide a new
> /etc/named.conf, I want to add a trigger that says that everytime it
> changes, "services named restart" should be invoked...
Yes, you can have the service "subscribe" to the configuration file:
service{"named":
.
.
.
subscribe=>File["/etc/named.conf"]
.
.
.
}
Or alternatively, a notify statement in the file resource type.
> 4 - Can the clients send a "deployed configuration successfully" msg
> to the server, so we keep a tally of
>
> - clients seen recently
> - success vs failure in deployment of latest config
> - what clients are failing or behind in their sync
At the most basic level, you can do this by simply enabling report =
true in clients' configuration and at the server reports = log. This
will log the required information in the puppet master's logs. There
are many more options for reporting, along with various tools (web
interfaces) like Dashboard & Foreman.
--
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.
