Maybe we''re the last to the party but wow do schedules make a huge difference! Especially with file serving. We added schedules to a few file-heavy modules and cut the load and hits/day on our file serving puppetmaster by 2/3. Instead of doing everything once an hour these modules are now scheduled to run just twice a day. --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Mark Plaksin wrote:> Maybe we''re the last to the party but wow do schedules make a huge > difference! Especially with file serving. We added schedules to a few > file-heavy modules and cut the load and hits/day on our file serving > puppetmaster by 2/3. Instead of doing everything once an hour these > modules are now scheduled to run just twice a day.Have you got a url on schedules? I''m not familiar with it, unless this is just a term for some technique of using cron? -- +-Geoff Crompton +--Debian System Administrator +---Trinity College --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Geoff Crompton wrote:> Mark Plaksin wrote: >> Maybe we''re the last to the party but wow do schedules make a huge >> difference! Especially with file serving. We added schedules to a few >> file-heavy modules and cut the load and hits/day on our file serving >> puppetmaster by 2/3. Instead of doing everything once an hour these >> modules are now scheduled to run just twice a day. > > Have you got a url on schedules? I''m not familiar with it, unless this > is just a term for some technique of using cron? > >http://reductivelabs.com/trac/puppet/wiki/TypeReference#id275 Regards James Turnbull -- Author of: * Pro Linux Systems Administration (http://www.amazon.com/gp/product/1430219122/) * Pulling Strings with Puppet (http://www.amazon.com/gp/product/1590599780/) * Pro Nagios 2.0 (http://www.amazon.com/gp/product/1590596099/) * Hardening Linux (http://www.amazon.com/gp/product/1590594444/)
James Turnbull wrote:> Geoff Crompton wrote: >> Mark Plaksin wrote: >>> Maybe we''re the last to the party but wow do schedules make a huge >>> difference! Especially with file serving. We added schedules to a few >>> file-heavy modules and cut the load and hits/day on our file serving >>> puppetmaster by 2/3. Instead of doing everything once an hour these >>> modules are now scheduled to run just twice a day. >> Have you got a url on schedules? I''m not familiar with it, unless this >> is just a term for some technique of using cron? >> >> > > http://reductivelabs.com/trac/puppet/wiki/TypeReference#id275 > > Regards > > James Turnbull >Ok, assuming I''ve got in site.pp schedule { maint: range => "2 - 4", period => daily, repeat => 1 } How do I use that in other classes and resources? The Language tutorial http://reductivelabs.com/trac/puppet/wiki/LanguageTutorial doesn''t mention them. Do you do something like: cron { ''a_beaut_cronjob'': cmd => ''echo foo'', requires => Schedule[ maint ], } -- +-Geoff Crompton +--Debian System Administrator +---Trinity College --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Hey, Geoff Crompton wrote:> How do I use that in other classes and resources? The Language tutorial > http://reductivelabs.com/trac/puppet/wiki/LanguageTutorial doesn''t > mention them.The TypeReference page does. Check the exec {} type in the example: exec { "/usr/bin/apt-get update": schedule => daily } cYa, Avi --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Avi Miller wrote:> Hey, > > Geoff Crompton wrote: >> How do I use that in other classes and resources? The Language tutorial >> http://reductivelabs.com/trac/puppet/wiki/LanguageTutorial doesn''t >> mention them. > > The TypeReference page does. Check the exec {} type in the example: > > exec { "/usr/bin/apt-get update": > schedule => daily > } > > cYa, > AviAhh, it''s a metaparameter documented at http://reductivelabs.com/trac/puppet/wiki/TypeReference#id343 Now that I read that bit, it does seem a little familiar. -- +-Geoff Crompton +--Debian System Administrator +---Trinity College --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
I''ve been looking at using schedules as a way of speeding up Puppet catalog runs, but its got one small(ish) annoyance. It would be nice to have the ability to confirm the existance of the file on one schedule, while validating the content/ attributes on another - the idea being that an objects existance/non-existance may need to be maintained more vigourously than its content. An obvious example for this would be for a user - if it doesn''t exist it needs to be created quickly as other items will depend on it, but the user resource itself doesn''t change much, so confirming that the settings are right once created can be done a less often. This could be especially true if there are things that depend on the objects existance - like packages, SSH keys and the like. Greg On Jun 2, 5:11 pm, Geoff Crompton <geo...@trinity.unimelb.edu.au> wrote:> Avi Miller wrote: > > Hey, > > > Geoff Crompton wrote: > >> How do I use that in other classes and resources? The Language tutorial > >>http://reductivelabs.com/trac/puppet/wiki/LanguageTutorialdoesn''t > >> mention them. > > > The TypeReference page does. Check the exec {} type in the example: > > > exec { "/usr/bin/apt-get update": > > schedule => daily > > } > > > cYa, > > Avi > > Ahh, it''s a metaparameter documented athttp://reductivelabs.com/trac/puppet/wiki/TypeReference#id343 > > Now that I read that bit, it does seem a little familiar. > > -- > +-Geoff Crompton > +--Debian System Administrator > +---Trinity College--~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---