On Mon, Jan 23, 2012 at 5:14 PM, Michael Stahnke <[email protected]> wrote: > 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.
Hi Michael, I knew that I could point to a proxy - but I am looking for ways to automate the setup. Hardcoding yum or apt proxies is not a very "Puppet" way of setting things up. If someone has 100 machines on EC2, then I am sure it would be way more efficient to pull the package once into EC2, cache it on the puppet master, and then redistribute it to all of the 100 machines. And when the master finds that every machine has the package installed, it can retire the package and free up space (with an ordinary proxy it is harder to do the retirement part) - of course if it is needed again it needs to be pulled in again. If the package provider layer can handle all the work of caching, then that would save lots of time - not every site wants to reinvent the wheel of package caching. Rayson ================================= Open Grid Scheduler / Grid Engine http://gridscheduler.sourceforge.net/ Scalable Grid Engine Support Program http://www.scalablelogic.com/ > > 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. > -- 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.
