On Fri, 2007-05-25 at 09:16 -0500, Mike McGrath wrote: > Over the last couple of weeks we've been using puppet to distribute > static content across some of our application servers and proxy servers. > > Static content might include the new static webpage or an application > like our accounts system. > > This has proved to be a bit of an issue. Puppet wasn't really designed > to do this and as such puts a noticeable load on the boxes while running > as well as causing longer runs. Puppet works for this but we're > currently into it managing thousands of files and initial deploys take a > long time :) In the past we'd discussed moving some things (like > turbogears apps) around using rpms. We can do that with tg pretty > easily. But what about other static content, images, things like that? > > This needs to be scriptable from start to finish, here's the options as > I see them: How about you use the puppet cert it makes on the client for auth and see if we can have wget or urlgrabber or curl use it to talk to mod_auth_cert on apache. Then we'd have a secure-auth + good static content replication. -sv
