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 > this is true if plugin sync is enabled, it also syncs custom types and providers if they exist. > 3. Client runs Facter (including the custom facts) > 4. Client sends output of Facter back to server > the client sends its facts along with its request for a catalog. > 5. Server builds the manifest to send to client based on Facter outputle > facts are available to the manifests at compile time as top scope variables (like ::operatingsystem) > 6. Client applies manifest from server. > > client applied the catalog, not the manifests. > 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]<puppet-users%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > -- 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.
