We use mco puppet runall 1 (our master is slightly anemic) in an every hour
cron job. We have few enough hosts that they can all run within the hour.
It's not quite as nice as the commander, as the commander would start
running them all immediately after the last one was done, but it works for
our purposes.
On Friday, February 8, 2013 10:44:51 AM UTC-8, Jo wrote:
> 3. There's no documented best way to run puppet from cron.
>
> I suspect PL hasn't put down a recipe for this since Puppet Commander
> hasn't been updated to work with Puppet 3 yet. That's probably the answer,
> but it's not available yet. This might be a good reason to wait.
>
> We settled on the many-year-old version of running it from cron with
> fqdn_rand(30). Given the numerous problems with the cron resource, we did
> this in a separate cron.d file like so:
>
> # two variables to control puppet run time
> $first_minute = fqdn_rand(30)
> $second_minute = $first_minute + 30
> file { "/etc/cron.d/puppet":
> owner => root,
> group => root,
> mode => 0444,
> content => template('puppet/cron-puppet'),
> require => Package['puppet'],
> }
>
> There might be a better way, but I couldn't find it. I'd really like to
> see a "best practice" recommendation from PuppetLabs.
>
> --
> Jo Rhett
> Net Consonance : net philanthropy to improve open source and internet
> projects.
>
--
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 puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
