On Sep 8, 2010, at 11:00 AM, Martin Langhoff wrote:
>>> 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":
>
> And I assume that it knows that on Fedora the magic incantation is
> service <servicename> restart...
That doesn't matter because puppet know how to do it.
> That'll only work if the file is updated by Puppet, correct? Or is
> there an inotify side to Puppet that I didn't know before...?
That will only work if the file is updated by puppet.
> If the service is sub'd to several files, and all are updated "in one
> go" from Puppet, will there be one service restart, or one per file?
Once per run.
>>> 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
>
> Hmmm... from what I've seen, that gets me when the puppet client
> _requested_ stuff, but not a "puppet client deployed successfully".
>
> Am I missing something?
This sends a report from the client to the server at the end of a run telling
the server what itthe client did including any errors applying a manifest.
>> like Dashboard & Foreman.
>
> Will investigate ;-)
--
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.
