On Mon, Jan 23, 2012 at 1:21 PM, Rayson Ho <[email protected]> wrote: > While Puppet allows us to manage a large number of instances on EC2, > what are the best practices for caching packages on EC2?? > > Instead of manually configuring yum or apt proxies on each node, it > would save us lots of time if caching could be "somehow" handled by > Puppet. Are there any plans to add the ability to handle caching in > the package providers??
How would Puppet handle it? It would still have to either cache the package locally (eating lots of disk space) or point to a proxy, which you can do with Puppet already. Your simplest solution might be to look for a mirror hosted in EC2, which I assume there are some. Another option would be to build up a squid proxy via puppet and then configure a client-side usage of that cache, but that's no different in EC2 vs any other setup. > > Rayson > > ================================= > Open Grid Scheduler / Grid Engine > http://gridscheduler.sourceforge.net/ > > Scalable Grid Engine Support Program > http://www.scalablelogic.com/ > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
