On Wed, May 19, 2010 at 11:04 AM, Jeff Falgout <[email protected]> wrote: > Group - > > I'm putting a presentation together for $work (a large .gov) and I want to > make sure I get my facts (pun intended) straight ... > Are the following steps for Facter-Client-Server interaction correct (I have > a feeling not): > 1. Client puppet run is initiated (via regular schedule, puppetrun, or > puppetd) > 2. The client contacts the server and downloads any custom facts it does not > already have
I think this is more accurately described as "synchronizing the local custom fact store from the server" as existing facts that are no longer on the server will be removed by the pluginsync. > 3. Client runs Facter (including the custom facts) > 4. Client sends output of Facter back to server > 5. Server builds the manifest to send to client based on Facter output > 6. Client applies manifest from server. > Thanks for any feedback, > Jeff > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" 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-users?hl=en. > -- nigel -- You received this message because you are subscribed to the Google Groups "Puppet Users" 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-users?hl=en.
