Thanks for the response. I shall look into the scheduler.
- Ranga On Tuesday, January 7, 2014 6:44:14 AM UTC-8, jcbollinger wrote: > > > > On Monday, January 6, 2014 7:09:01 PM UTC-6, [email protected]: >> >> Hi >> >> I am trying to wrap my head around how best to implement the following >> functionality: >> >> - Get information about puppet agent runs as soon as they complete >> - Some kind of a callback mechanism would be ideal >> >> > Calling back to whom? Seriously, I'm not just being picky. I know well > what a callback is in general, but I don't understand what you mean by that > in this context. That leaves me uncertain of the characteristics of your > ideal solution. > > > >> Could this be done by creating an "exported" resource? >> > > > No. Exported resources could conceivably be used to provide information > about catalog compilation, but they have no visibility into details or > completion status of agent runs. > > > >> Or could it be achieved using MCollective? >> > > > Only if you are using MCollective to perform agent runs (in non-daemon > mode) in the first place. If you are running the agent in daemon mode or > via an ordinary scheduler (e.g. cron) then how would MCollective have any > clue? > > > >> Any pointers around this is appreciated. >> >> > > Puppet's built-in reporting mechanism might serve your purpose, as > Aurélien suggested. Alternatively, if you run via a scheduler then you > could put a wrapper script around the agent invocation that sends whatever > information you like, by whatever means you like. > > > John > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/c08af660-651f-4009-845c-9bcd093ebc77%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
