Puppet users - Oct 2006 - How do I manage manifests most efficiently...?

Hi

As I''m more familiar with cfengine and it''s way to split
updates (in
update.conf) from the actual grunt work (in cfagent.conf), I''m  
wondering how to best manage puppet and my manifests with puppet...?

Should I define a puppet class that copy the puppet package (in .tgz  
format) and all the manifests to the client, and then have all my  
other classes depend on that (sort of what I do now, except that it  
only copies the manifests - not the puppet package, and I haven''t  
made any of the other classes dependent on the puppet class). Or has  
puppet a nifty way to handle that.

With my current solution, it takes two runs of puppetd to actually  
run the new code - one to copy it from the server, and one to execute  
it...


--
Med venlig hilsen
Juri Rischel Jensen

Fab:IT ApS
Vesterbrogade 50
DK-1620 København
Tlf: 70 202 407 / Fax: 33 313 640
www.fab-it.dk / juri@fab-it.dk

Hi,

Why don''t you use puppet in client-server mode? You don''t need
to copy
the manifests on each client in that mode.

2006/10/14, Juri Rischel Jensen <juri@fab-it.dk>:
> Hi
>
> As I''m more familiar with cfengine and it''s way to split
updates (in
> update.conf) from the actual grunt work (in cfagent.conf), I''m
> wondering how to best manage puppet and my manifests with puppet...?
>
> Should I define a puppet class that copy the puppet package (in .tgz
> format) and all the manifests to the client, and then have all my
> other classes depend on that (sort of what I do now, except that it
> only copies the manifests - not the puppet package, and I haven''t
> made any of the other classes dependent on the puppet class). Or has
> puppet a nifty way to handle that.
>
> With my current solution, it takes two runs of puppetd to actually
> run the new code - one to copy it from the server, and one to execute
> it...
>
>
> --
> Med venlig hilsen
> Juri Rischel Jensen
>
> Fab:IT ApS
> Vesterbrogade 50
> DK-1620 København
> Tlf: 70 202 407 / Fax: 33 313 640
> www.fab-it.dk / juri@fab-it.dk
>
>
>
> _______________________________________________
> Puppet-users mailing list
> Puppet-users@madstop.com
> https://mail.madstop.com/mailman/listinfo/puppet-users
>

On Oct 15, 2006, at 10:59, Sébastien Prud''homme wrote:
> Why don''t you use puppet in client-server mode? You don''t
need to copy
> the manifests on each client in that mode.
Does that mean that the server parses the manifests and serves them  
to the client upon request...?

Right now I''m testing with one machine, and have all my manifests in / 
srv/puppet together with all the configfiles I wan''t to ditribute. I  
have my client (which is also my server) copy all relevant  
configfiles to /etc - including my manifests to /etc/puppet/ 
manifests. But as I understand your answer above, I don''t have to  
copy my manifests to the client...?


--
Med venlig hilsen
Juri Rischel Jensen

Fab:IT ApS
Vesterbrogade 50
DK-1620 København
Tlf: 70 202 407 / Fax: 33 313 640
www.fab-it.dk / juri@fab-it.dk

Juri Rischel Jensen wrote:
> 
> Does that mean that the server parses the manifests and serves them  
> to the client upon request...?
Basically, yes; the server actually compiles a per-client configuration, 
so the client only sees as much of the configuration as it needs to do 
its job.
> Right now I''m testing with one machine, and have all my manifests
in /
> srv/puppet together with all the configfiles I wan''t to ditribute.
I
> have my client (which is also my server) copy all relevant  
> configfiles to /etc - including my manifests to /etc/puppet/ 
> manifests. But as I understand your answer above, I don''t have to
> copy my manifests to the client...?
Right.  You just start puppetmasterd pointed at your manifests (using 
--manifest), then run puppetd pointed at your server (using --server).

On each run, the server will recompile the configuration and just send 
the results, rather than the whole configuration.

-- 
2.  If 2 + 2 is 4 and 2 x 2 is also 4, what''s the big deal
     about multiplication anyway?
                 -- from the Dogbert''s New Ruling Class quiz
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com

On Oct 15, 2006, at 21:53, Luke Kanies wrote:
>> Does that mean that the server parses the manifests and serves them
>> to the client upon request...?
>
> Basically, yes; the server actually compiles a per-client  
> configuration,
> so the client only sees as much of the configuration as it needs to do
> its job.
Wauvv! As I get to know puppet better, I like it more and more. This  
actually adresses one of my biggest concerns about using automated  
configuration management that''s centrally managed, in our shop where  
we have a mix of rented servers with systems management, customer  
servers with systems management etc: Exposing all configuration  
information to all customers.
>> Right now I''m testing with one machine, and have all my
manifests
>> in /
>> srv/puppet together with all the configfiles I wan''t to
ditribute. I
>> have my client (which is also my server) copy all relevant
>> configfiles to /etc - including my manifests to /etc/puppet/
>> manifests. But as I understand your answer above, I don''t have
to
>> copy my manifests to the client...?
>
> Right.  You just start puppetmasterd pointed at your manifests (using
> --manifest), then run puppetd pointed at your server (using --server).
>
> On each run, the server will recompile the configuration and just send
> the results, rather than the whole configuration.
Once again: Wauvv!

--
Med venlig hilsen
Juri Rischel Jensen

Fab:IT ApS
Vesterbrogade 50
DK-1620 København
Tlf: 70 202 407 / Fax: 33 313 640
www.fab-it.dk / juri@fab-it.dk