Issue #4486 has been updated by konrad rzentarzewski.
is it dead? or fixed long ago and not updated in docs/redmine? ---------------------------------------- Feature #4486: server-side (puppetmaster) catalogue caching https://projects.puppetlabs.com/issues/4486#change-56142 Author: Robin Bowes Status: Accepted Priority: High Assignee: Category: plumbing Target version: Affected Puppet version: Keywords: Branch: I'd like to see some sort of catalogue caching in puppetmaster, so it can handle more requests. The use case is deploying a config change across many machines in parallel. At the moment, it is not possible to deploy to a large number of machines simultaneously - puppetmaster can't take the load. I'd like to be able to do this: 1. disable puppetmaster (ie. prevent clients from getting updated catalogues) 2. make configuration changes (update modules, manifests, etc.) 3. Pre-generate catalogs for all clients and cache them so they are not re-generated next time the client connects 4. Trigger a puppet run on all clients. They will connect and get the cached catalogue, which should be a fairly lightweight process compared to compiling the whole catalogue Thoughts? -- 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://projects.puppetlabs.com/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.
