I''m trying to get a feel for the actual use cases for the Schedule type in Puppet. Anyone care to help me out with some real world examples? -- 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.
On Mon, Jan 17, 2011 at 18:38, Nigel Kersten <nigel@puppetlabs.com> wrote:> I''m trying to get a feel for the actual use cases for the Schedule type in > Puppet. Anyone care to help me out with some real world examples?At my previous job we planned to used them to control update periods for production software: we would commit to a specific maintenance window with a client, then set puppet to install the latest version of a package (from our private repo) then use schedule to ensure that happened automatically only during that period. That would allow us to make other changes to the production systems through puppet (and, more importantly, ensure that monitoring and backups were correctly functional) without having to schedule the push of software through the repository. The only reason it didn''t roll out was that we didn''t get time to take our prototype to full production, so I would imagine they are there by now. Regards, Daniel -- ✉ Daniel Pittman <daniel@rimspace.net> ⌨ daniel@rimspace.net (XMPP) ☎ +1 503 893 2285 ♻ 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-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.
This is exactly what we used schedules for. System software.was.only updated at specific times to ensure that we got the maximum io from our disks. On Jan 17, 2011 6:50 PM, "Daniel Pittman" <daniel@rimspace.net> wrote: On Mon, Jan 17, 2011 at 18:38, Nigel Kersten <nigel@puppetlabs.com> wrote:> I''m trying to get a fee...At my previous job we planned to used them to control update periods for production software: we would commit to a specific maintenance window with a client, then set puppet to install the latest version of a package (from our private repo) then use schedule to ensure that happened automatically only during that period. That would allow us to make other changes to the production systems through puppet (and, more importantly, ensure that monitoring and backups were correctly functional) without having to schedule the push of software through the repository. The only reason it didn''t roll out was that we didn''t get time to take our prototype to full production, so I would imagine they are there by now. Regards, Daniel -- ✉ Daniel Pittman <daniel@rimspace.net> ⌨ daniel@rimspace.net (XMPP) ☎ +1 503 893 2285 ♻ made with 100 percent post-consumer electrons -- You received this message because you are subscribed to the Google Groups "Puppet Users" group.... -- 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.
in the past I used them for large dir syncs that takes a lot of time and dont change that often.... Ohad On Tue, Jan 18, 2011 at 4:38 AM, Nigel Kersten <nigel@puppetlabs.com> wrote:> I''m trying to get a feel for the actual use cases for the Schedule type in > Puppet. > > Anyone care to help me out with some real world examples? > > -- > 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<puppet-users%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. >-- 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.
On Mon, 2011-01-17 at 18:38 -0800, Nigel Kersten wrote:> I''m trying to get a feel for the actual use cases for the Schedule > type in Puppet.Can you elaborate?> Anyone care to help me out with some real world examples?I''m using schedules so that my puppetd run "apt-get update" only once per day. -- Brice Figureau Follow the latest Puppet Community evolutions on www.planetpuppet.org! -- 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.
On Tue, Jan 18, 2011 at 8:50 AM, Brice Figureau < brice-puppet@daysofwonder.com> wrote:> On Mon, 2011-01-17 at 18:38 -0800, Nigel Kersten wrote: > > I''m trying to get a feel for the actual use cases for the Schedule > > type in Puppet. > > Can you elaborate? >I''ve never used them much, people don''t talk about them a lot, and I want to get a feel for what people use them for :)> > > Anyone care to help me out with some real world examples? > > I''m using schedules so that my puppetd run "apt-get update" only once > per day.Interesting. How do you deal with pushing out a new repository?>-- 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.
On 18/01/11 18:12, Nigel Kersten wrote:> On Tue, Jan 18, 2011 at 8:50 AM, Brice Figureau > <brice-puppet@daysofwonder.com <mailto:brice-puppet@daysofwonder.com>> > wrote: > > On Mon, 2011-01-17 at 18:38 -0800, Nigel Kersten wrote: > > I''m trying to get a feel for the actual use cases for the Schedule > > type in Puppet. > > Can you elaborate? > > > I''ve never used them much, people don''t talk about them a lot, and I > want to get a feel for what people use them for :)I think this is an under-estimated feature most people don''t know about.> > > Anyone care to help me out with some real world examples? > > I''m using schedules so that my puppetd run "apt-get update" only once > per day. > > > Interesting. How do you deal with pushing out a new repository?I''m afraid it never happened, so I never cared :) But I suppose you can temporarily add a resource override with schedule => undef -- Brice Figureau My Blog: http://www.masterzen.fr/ -- 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.
----- Original Message -----> On 18/01/11 18:12, Nigel Kersten wrote: > > On Tue, Jan 18, 2011 at 8:50 AM, Brice Figureau > > <brice-puppet@daysofwonder.com > > <mailto:brice-puppet@daysofwonder.com>> > > wrote: > > > > On Mon, 2011-01-17 at 18:38 -0800, Nigel Kersten wrote: > > > I''m trying to get a feel for the actual use cases for the > > > Schedule > > > type in Puppet. > > > > Can you elaborate? > > > > > > I''ve never used them much, people don''t talk about them a lot, and I > > want to get a feel for what people use them for :) > > I think this is an under-estimated feature most people don''t know > about.I tend to avoid since things like making sure apt caches are up to date can in some cases be considered critical so I''d rather add a cron job for it rather than rely on a much more complex subsystem to work in order for this important thing to happen. so far whenever I thought I''d use schedule I reconsidered cos the things I wanted to schedule was important, no doubt its sufficient in some cases but thats been my experience.> > > > > > Anyone care to help me out with some real world examples? > > > > I''m using schedules so that my puppetd run "apt-get update" only > > once > > per day. > > > > > > Interesting. How do you deal with pushing out a new repository? > > I''m afraid it never happened, so I never cared :) > But I suppose you can temporarily add a resource override with > schedule > => undef-- R.I.Pienaar -- 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.
On Jan 17, 6:38 pm, Nigel Kersten <ni...@puppetlabs.com> wrote:> I''m trying to get a feel for the actual use cases for the Schedule type in > Puppet. > > Anyone care to help me out with some real world examples?Schedules go great with exported resources. My use case is getting applied changes on machines A-N because of a resource change on machine M, which may be exporting only. Using Sshkey as an example a new machine would cause a thousand other machines in its environment to update on their next run. Then, on the new machines second run it updates for its own key. In a busy environment that would pretty much ensure every run on every host applied changes, which I dont like to see. My other example, as people have noted, is to respect maintenance windows. I can think of httpd virtual hosts, DNS updates, & monitoring system updates that could be affected by schedules. -- 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.