Ethan Rowe wrote: >> 1. Configuration should all run out of puppet.conf - no new files for >> this (I am assuming that was the intent). > > Since the message service particulars will need to be shared by at least > daemons (puppetmaster, puppetqd), it makes sense to place those > particulars in a common location.
Agreed - puppet.conf seems the logical choice. > The working design absolutely takes these considerations to heart. > Yesterday I did some fledgling implementation for the abstract terminus, > the client registry, etc., and I'm taking the trouble to document as I go. > > Whether my documentation is comprehensible is another matter, but the > effort has been and will continue to be there. Let me know and I can work on it. It's probably what I can best contribute. >> 4. What happens with the queue daemon breaks in the process? > > To be sure I understand what you're asking, did you perhaps mean "when > the queue daemon breaks" rather than "with"? Yes - sorry s/with/when/ > A diagram would presumably help quite a lot. Words can express the > design, but the abstractions are of the sort that will tend to lose a > reader. Again - if someone does a rough one I can polish if required. It'd probably be an excuse for me to do a bunch for various processes. I had intended to do such for the new wiki. Cheers James -- Author of: * Pulling Strings with Puppet (http://www.amazon.com/gp/product/1590599780/) * Pro Nagios 2.0 (http://www.amazon.com/gp/product/1590596099/) * Hardening Linux (http://www.amazon.com/gp/product/1590594444/)
signature.asc
Description: OpenPGP digital signature
