----- "Paul Berry" <[email protected]> wrote: > 1. Make low-end scaling easier: currently when a customer's deployment > gets too large to be handled by a single master running Webrick, they > have to install apache/passenger or mongrel. This can be difficult to > do, especially since passenger has limited package support on some > OSes (notably RHEL/Centos 5). It would be nice to give people a less > painful way of scaling up beyond what Webrick is capable of handling.
I'd agree with Brice here, using Passenger would still be the easy option here. > 4. Make Puppet handle load spikes more robustly. Currently I > understand from Luke that there is an avalance effect once the master > reaches 100% capacity, wherein the machine starts thrashing and > actually loses throughput, causing further load increases. It would be > nice if we could guarantee that Puppet didn't try to serve more > simultaneous requests than its processors/memory could handle, so that > performance would degrade more gracefully in times of high load. Great, and this is easy with middleware. > 6. Allow a "push model", where changing the manifest causes catalogs > to be recompiled, and those catalogs are then pushed out to client > machines rather than waiting for the client machines to contact the > master and request catalogs. This would require those clients to run a daemon that talks directly to the bus, or would you want some kind of puppet kick style system still for this? -- R.I.Pienaar -- 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.
