On Thu, Jun 9, 2011 at 3:15 AM, Dean Wilson <dwil...@unixdaemon.net> wrote:
> On Wed, Jun 08, 2011 at 05:50:58PM -0700, Josh Cooper wrote: > > > It'd be great to hear about your experience with the pre/post run > > commands and what use cases you are trying to solve. > > We use the feature to generate additional information about how the > puppet run has changed the system: > > http://www.unixdaemon.net/tools/puppet/nagios-wrapped-puppet-runs.html > > In our use case we're only using the two stages as information hooks for > their side-effects - not to alter the puppet run. > > > Also, is there anything that is being solved with pre/post run > > commands that can't be solved using stages? For example, if the prerun > > command, catalog, and postrun commands are executed as stages, in that > > order, with each stage depending on its predecessor(s), it would > > ensure that: > > For my example usage I could quite easily move the commands to be execs > in the pre and post stages. > One use of pre commands that isn't solved with stages is to check "Should I even do a Puppet run right now?" or anything else that is out of band in a similar sense. I used to do this in a wrapper script where the nodes would basically look and see if the masters were all under too much load to serve this node or not, or to check whether puppet runs had been disabled centrally, but ideally this would just be a prerun command. -- Nigel Kersten Product, Puppet Labs @nigelkersten -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
