On Mon, Dec 22, 2008 at 01:21:23PM -0600, Evan Hisey wrote: > > On Mon, Dec 22, 2008 at 1:02 PM, Robin Lee Powell > <rlpow...@digitalkingdom.org> wrote: > > > > On Mon, Dec 22, 2008 at 10:40:05AM +0100, Peter Meier wrote: > >> > >> Hi > >> > >> > Debug output of the client run follows. No, I didn't update the > >> > master; why would I do that? This is about functionality on the > >> > client, not the master. Is it actually necessary that the > >> > *master* have Augeas when it never uses it? > >> > >> well the master has to compile the manifest with all it's > >> dependencies and it will send the evaluated manifest down to the > >> client. IMHO therefore it have to know the new type. > > > > Well, that seemed to do it. Just strikes me as odd. Thank you! > > > Why does it strike you as odd? The server does all the heavy > lifting. By the time it gets to the client all you have are set of > directions to be followed. The idea of a Puppet and a PuppetMaster > is really an accurate view of the system
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: In particular, Puppet is usually used in a star formation, with all of your clients talking to one or more central servers. Each client contacts the server periodically (every half hour, by default), gets its latest configuration, and makes sure it is in sync with that configuration. Once done, it can send a report back to the server indicating what, if anything, happened which is exactly what I thought: the server delivers the configurations, and the client does what they say. The server, as described there, shouldn't care at all what the configurations *say*. (Neither of those pages even contain the text "master", by the way.) So, now I "know" that puppet doesn't work like that (proof by existence and all that), but I have no idea what the puppetmaster actually *does* anymore. That is, you say "By the time it gets to the client all you have are set of directions to be followed.", which is what I thought, but I thought the "set of directions" was things like: augeas { "no usecacheonfailure" : context => "/files/etc/puppet/puppet.conf", changes => "set main/usecacheonfailure false", } that the client then dealt with themselves. Pointers to what puppetmaster *actually* sends the clients would be welcome. -Robin -- They say: "The first AIs will be built by the military as weapons." And I'm thinking: "Does it even occur to you to try for something other than the default outcome?" -- http://shorl.com/tydruhedufogre http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
