On Sun, Nov 6, 2011 at 5:57 AM, Piavlo <lolitus...@gmail.com> wrote: > > Hi , > > How about an option for throttling number of max puppet clients being > active - then puppet client time to run has come it registers at the > puppetmaster - and once there is below max allowed active puppet clients > running - puppetmaster initiates the client run (puppet client needs to > have "listen=true" for that to work). Priorities can also be added easily. > This also gives you easy visibility on then running puppet every X minutes > becomes a bottleneck. > This ca be probably done with mcollective - but requires a separate daemon > process to manage the queue waiting puppet clients. > The advanate of separate daemon is that it can have a view of more than > one puppetmaster. > The disadvantage is that puppet clients can still connect directly > puppetmaster avoiding the queue altogether. > So it looks like a builtin puppet queue functionality is a better choice. > > wdyt? >
So you need a queue *somewhere* to do this, and MCollective will do this for you now with the "mco puppetd runall X" agent. Your point about agents still being able to connect if they want to is a good one though. I'd love it if you filed this as a feature request though Piavlo, it's important to capture this somewhere outside the mailing lists. -- Nigel Kersten Product Manager, Puppet Labs -- 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.
