----- Original Message ----- > From: "Hailee Kenney" <hai...@puppetlabs.com> > To: puppet-dev@googlegroups.com > Sent: Wednesday, May 23, 2012 11:31:55 PM > Subject: [Puppet-dev] External cache for fact values > > > We are implementing caching in Facter, and are looking for feedback > on how we've decided to do so. As further described in this ticket , > we've deciding against an internal cache because it's really hard to > get right in a concurrent environment. > > > Our supported interface will be a simple yaml file on disk using only > key/value pairs with out-of-band updates. > > > This will allow us to decouple the cache from the implementation of > updating the cache, which will allow us to potentially transition to > a daemonized version of Facter which can do piecemeal expiration of > individual facts rather than replacement of the entire cache. The > update method today might be cron, but it allows us some flexibility > it how we do the updates.
can you give some more detail on how the cache will be used? If a fact is found on disk via the rb file and there's nothing in the cache will it then simply run the slow way? and update the cache? sounds like there would be various chicken and egg situations with arranging for pluginsync to have happened before attempts to build the cache so I am looking to hear some more details to determine if that might be an issue. There is a definite need for varying ttl times - totalmemory can have a long ttl while something like EC2 facts might have a lower TTL > > > This method has been proven effective in MCollective. I wouldnt go so far as saying that :) generating fact caches via cronjob or puppet writing out yaml files has been a recurring headache for people -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to puppet-dev@googlegroups.com. To unsubscribe from this group, send email to puppet-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
