I went through all the ''getting started'' stuff, and have a puppetmaster and several test clients configured. I''m not clear as to how the puppetmaster manages the puppet configurations on the clients ... while it would obviously be possible to add puppet.conf as a distributed file, I''m guessing there''s probably a better way to manage this sort of thing? Specifically, if I want to do something like change ''runinterval'' or ''splay'' on all the clients, what would be the standard way of doing it? I''m guessing this info is contained in the missing file ''reductivelabs.com/trac/puppet/wiki/ MasterConfigLayout'' ...
--On Monday, August 20, 2007 12:18:19 PM -0700 Michael Stevens <m@tippett.com> wrote:> I went through all the ''getting started'' stuff, and have a > puppetmaster and several test clients configured. I''m not clear as to > how the puppetmaster manages the puppet configurations on the > clients ... while it would obviously be possible to add puppet.conf > as a distributed file, I''m guessing there''s probably a better way to > manage this sort of thing? Specifically, if I want to do something > like change ''runinterval'' or ''splay'' on all the clients, what would > be the standard way of doing it? I''m guessing this info is contained > in the missing file ''reductivelabs.com/trac/puppet/wiki/ > MasterConfigLayout'' ...I find that the default puppet config is sufficient to do the initial contact to the puppetmaster, during which time it gets a puppet.conf that I want it to use.
Michael Stevens wrote:> manage this sort of thing? Specifically, if I want to do something > like change ''runinterval'' or ''splay'' on all the clients, what would > be the standard way of doing it? I''m guessing this info is containedI did that by means of modifying the Debian package for a custom Debian-based distribution, but that''s not the best solution for all cases. I think I''d stick with Digant''s advice of having the puppetmaster manage a distributed puppetd.conf file. Jose