----- Original Message ----- > From: "Ken Barber" <k...@puppetlabs.com> > To: puppet-dev@googlegroups.com > Sent: Friday, May 25, 2012 11:38:35 AM > Subject: Re: [Puppet-dev] External cache for fact values > > >> 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? > >> > > Facter itself will not use the cache. If you have an application > > that needs > > facts and needs them quickly, you may read the yaml file on disk. > > An > > entirely separate process will update the cache. At this first > > step, the > > update process is planned to be a cron job, with hope of an actual > > facter > > daemon later. > > Err ... really? So we're not changing what we do at all today then? > People have been rolling facilities like this for quite some time > already (ie. with mcollective and yaml plugin), it doesn't seem like > we're adding much value at all. And from memory PE already does this. > I mean a cron job with: > > facter -y > /var/lib/facter/cache.yaml > > Is already do-able. So what I'm failing to understand is ... what are > the changes in facter we are proposing today then?
I am also very confused, it seems this is a non feature and not needed if it's not going to provide any actual caching to facter -- 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.
