Issue #2049 has been updated by luke.
I totally like this idea, and have been wanting to do it for a long time. I've even got an idea for how to make it work with files, although it's a bit messy to explain. Basically, you have file sources expand at compile time, so that that catalog, as cached on disk, contains everything you need to know about a remote file other than its content -- instead it has an md5 sum. Then your client's filebucket caches all files that it cares about locally. That is, the catalog is searched for files, and any that specify source as a checksum (or something; this is going to require a change in specification, I think) will be downloaded when the catalog is retrieved. That way, if any files need to get replaced (because they've been modified locally) they can get replaced from the local file bucket (which just operates like a file cache in this case), rather than having to hit the server. This has the added benefit, even when not offline, of guaranteeing that your file contents only ever change in sync with your catalog - as it is now, you have a kind of race condition and could use a cached catalog but get new file contents. You'd also need a report queue -- something you can slap the reports in to get sent out when the client goes online. This offline functionality would probably be a bit useful without the local file serving or report queueing, but it would always be limited and throw a bunch of errors. ---------------------------------------- Feature #2049: Allow puppet to run in an offline mode that only uses the cache http://projects.reductivelabs.com/issues/2049 Author: nigelk2 Status: Accepted Priority: Normal Assigned to: Category: plumbing Target version: unplanned Complexity: Unknown Affected version: 0.24.7 Keywords: I've been poking at adding this feature for a while, so I thought I'd put in the feature request and see what the consensus is on what this option should be named, or whether there is violent disagreement as to whether it should exist. I want the ability to tell puppetd to only use the cache and not to talk to the server at all. That way we can schedule our laptop clients to still run puppet regularly to enforce security policies, but reduce load on our servers by only downloading a new catalog once or twice a day. This looks pretty simple to add, but I'm unsure as to the best name for this option. --usecacheonly --no-server ??? ---------------------------------------- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
