On Apr 9, 2008, at 1:28 PM, Adam Jacob wrote:
> > On Wed, Apr 9, 2008 at 9:57 AM, Luke Kanies <[EMAIL PROTECTED]> wrote: >> So, question 1: Do we just get rid of selective recompiling? If so, >> then you can stop reading. :) > > I vote for getting rid of it. > > I already run with --ignore-cache, since we're using an external node > tool that might cause changes that puppet doesn't pick up in the > normal course of things. > > As for the slowdown for people using stored configs, the right long > term answer here might be to write those storage requests out to a > queue instead of directly to the database anyway. That un-bundles the > act of feeding a client the manifest list from recording what has been > done for posterity. (You could even look at using my early > implementation of runnels to make this work, although it might be > overkill.) I think the long-term solution is to decouple storeconfigs from puppetmasterd (which Luke and I have talked a lot about), and have an external tool (puppetshow, iclassify, etc.) that can query puppetmasterd for node information via REST. In this scenario it would be great if there were a cache so that the external tools can query for only what's changed since <timestamp>. I think it would be A Bad Thing if a tool like this were to query for all nodes and puppetmasterd would have to compile everything every time. -Blake --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev?hl=en -~----------~----~----~----~------~----~------~--~---
