We're a Debian shop, with our own internal repository for controlling packages. We use the unattended-upgrades package to perform upgrades and use puppet to instantiate the whole process using a variant of the recipe at the bottom of this page:
http://reductivelabs.com/trac/puppet/wiki/Recipes/Debian - Jeff On 09/14/2009 03:12 PM, ELTigre wrote: > > On Sep 14, 1:56 pm, Peter Meier<peter.me...@immerda.ch> wrote: >> Hi >> >>> I'd like to know at what level we can use puppet to keep systems >>> up2date. I appreciate if you share some experiences. >>> :-) >> > Hi Pete, > Thanks for your soon answer, We've always updated packages of > principal services manually and other packages not so important > automatically using some cron jobs. BUT, puppet comes to play and we > have a lot of servers running in production environment. That's the > reason why I'm asking the list. The updating process is complicated > because you have to manually do the dirty job. We thought puppet can > handle this servers's update job. But I see it's not a good idea. > > Does anyone in the list use puppet to handle updates on servers? :-) > > regards, > Israel. >> we don't use puppet at all to keep systems up2date and I don't think >> it's a good idea either. Your package manager usually does a much better >> job. To manage bigger installations something like satellite or even an >> own managed package repository, which you sync with the upstream updates >> you need and then run a cron only against that repository might be a >> suitable solution. >> >> cheers pete > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
