Jeff McCune <j...@puppetlabs.com> writes:
> On Mon, Aug 23, 2010 at 4:54 PM, Daniel Pittman <dan...@rimspace.net> wrote:
>> Franck <ffallat...@gmail.com> writes:
>>
>>> So I've decided to use crontab for all my puppet clients rather than
>>> the daemon. I've set-up a puppetmaster with seven puppet clients.
>>>
>>> I'm using the following pattern:
>>>
>>> class cron {
>>> $minute = generate('/usr/bin/env', 'sh', '-c', 'printf $((RANDOM
>>> %60+0))')
>>
>> $minute = fqdn_rand(59)
>>
>> That generates a random, but consistent, number in the 0-59 range based on
>> the
>> name of the host. This will give some spread, but not the complete
>> randomness
>> of the method above.
>
> This seems overly complicated. Why not just have a bash wrapper script
> execute from cron and execute puppetd for you:
If you were going to do that, using splay might also make sense[1]. However,
that was already suggested earlier in the thread, and it doesn't give you a
predictable runtime for each node.
Personally, I would favour using the mcollective puppet execution director to
trigger off running on your nodes, but that is much, much further from where
the OP wanted to be and all. :)
Daniel
Footnotes:
[1] ...though it would presumably tie up more memory for longer, since
puppetd has a larger footprint than sleep(1) does.
--
✣ Daniel Pittman ✉ dan...@rimspace.net ☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@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.
