Puppet users - May 2010 - How Does the Interaction Between Facter, Clients, and the Server work

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
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 puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On 5/19/2010 8:04 PM, Jeff Falgout 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 ...
heh :)
> 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
> 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.

As far as I can see it, you''ve got it right. The only
"detail" I''d fix
is that the steps 4 and 5 are actually one http GET call and cannot be 
separated.



Best Regards, David
-- 
dasz.at OG              Tel: +43 (0)664 2602670     Web: http://dasz.at
Klosterneuburg                                         UID: ATU64260999

        FB-Nr.: FN 309285 g          FB-Gericht: LG Korneuburg

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Wed, May 19, 2010 at 11:04 AM, Jeff Falgout <jtfalgout@gmail.com>
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 puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
>
puppet-users+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@googlegroups.com>
> .
> 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 puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Wed, May 19, 2010 at 11:04 AM, Jeff Falgout <jtfalgout@gmail.com>
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 puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscribe@googlegroups.com.
> 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 puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Wed, May 19, 2010 at 12:30 PM, Nigel Kersten <nigelk@google.com> wrote:
> On Wed, May 19, 2010 at 11:04 AM, Jeff Falgout <jtfalgout@gmail.com>
> 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 puppet-users@googlegroups.com.
> > To unsubscribe from this group, send email to
> >
puppet-users+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@googlegroups.com>
> .
> > For more options, visit this group at
> > http://groups.google.com/group/puppet-users?hl=en.
> >
>
>
>
> Perfect - Thanks guys for the feedback and clarification.
>
Jeff

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.