Robin Lee Powell wrote: > Probably because I'm used to cfengine, where all the master does is > send the files to the clients that then do what the files say. > > I gather that's not how Puppet works, but looking at > http://reductivelabs.com/trac/puppet/wiki/BigPicture > and http://reductivelabs.com/trac/puppet/wiki/PuppetIntroduction I > see no indication to the contrary. In fact, the latter says:
"A Puppet server is aware of the full configuration. As some component's configuration aspects depend on the configuration of other components (e.g. the firewall config includes the ports used by webservers), generating configuration for a component *requires being aware of full configuration*." "Puppet Clients normally request or "pull" configuration from their server. The Server processes the configuration request for the host using a *pre-generated tree model* of the classes and definitions from the site-config." My emphasis. But yes not as clear as it could be. > Pointers to what puppetmaster *actually* sends the clients would be > welcome. I don't think the lifecycle is clearly documented anywhere. But if someone would like to string some words together I am happy to help them. Cheers James Turnbull -- 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
