Puppet users - May 2011 - at which size to use a "real" webserver

Hi,

I''m currently using puppet with the buildin server for testing on a few
nodes
(~5). But in the future my installation will be bigger. It will have about 110 
nodes of our compute cluster and maybe some additional servers (~20).
Currently I don''t use very complicated manifests and want to manage
only a few
config files, nfs mounts and the list of installed packages.

But maybe this list will grow with my love for puppet.
Should I already plan on using a different server? What would you recommend?
I will be using apache on one headnode anyway for ganglia & nagios.
Should I also move puppet to apache? How complicated is this?
I''m not familar with Ruby or Rails.

Btw. any suggestions for my bootstrapping install of puppet on Ubuntu? Here is 
my procedure:

1. minimal Ubuntu install using pxeboot with preseed file (from web-URL)
2. some postinstall config:
    - install facter and puppet from gems (loaded from web server)
    - install pre-created certs           (loaded from web server)
    - edit /etc/hosts to make puppet server known
3. start puppet for remaining configuration:
    - additional packages
    - nfsmount ...

regards, Andreas

-- 
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.

Hey Andreas,

Andreas Kuntzagk [Tue, May 03, 2011 at 12:21:34PM
+0200]:
> Btw. any suggestions for my bootstrapping install of puppet on
> Ubuntu? Here is my procedure:
> 
> 1. minimal Ubuntu install using pxeboot with preseed file (from web-URL)
This is probably always the same, getting the OS up is a seperate step
and in my opinion should be minimal [0].
> 2. [...]
I''m planning to do it with cdist[1], have a look in my post from
yesterday
(Subject: Puppet bootstrap: via cdist).

Cheers,

Nico

[0]
http://www.nico.schottelius.org/blog/configuration-installation-server-bootstrap/
[1] http://www.nico.schottelius.org/software/cdist/ 

-- 
PGP key: 7ED9 F7D3 6B10 81D7 0EC5  5C09 D7DC C8E4 3187 7DF0

-- 
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 Tue, May 3, 2011 at 11:21 AM, Andreas Kuntzagk
<andreas.kuntzagk@mdc-berlin.de> wrote:
> 1. minimal Ubuntu install using pxeboot with preseed file (from web-URL)
I use FAI personally, which enables me to automatically include the
puppet client and kick the 1st run. You could achieve the same thing
with preseed, kickstart etc.. I also use the debianized packages as
gems are a little more difficult to use when bootstrapping imho.

I also use passenger for *everything* (even testing). It''s really
simple to setup,
http://m.etrono.me/posts/5-simple-ish-puppet-infrastructure - a hell
of a lot of this could be puppetified, granted..



-- 
$ echo "kpfmAdpoofdufevq/dp/vl" | perl -pe
''s/(.)/chr(ord($1)-1)/ge''

-- 
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 Tue, May 3, 2011 at 9:00 AM, joel.merrick@gmail.com <
joel.merrick@gmail.com> wrote:
> On Tue, May 3, 2011 at 11:21 AM, Andreas Kuntzagk
> <andreas.kuntzagk@mdc-berlin.de> wrote:
>
> > 1. minimal Ubuntu install using pxeboot with preseed file (from
web-URL)
>
> I use FAI personally, which enables me to automatically include the
> puppet client and kick the 1st run. You could achieve the same thing
> with preseed, kickstart etc.. I also use the debianized packages as
> gems are a little more difficult to use when bootstrapping imho.
>
> I also use passenger for *everything* (even testing). It''s really
> simple to setup,
> http://m.etrono.me/posts/5-simple-ish-puppet-infrastructure - a hell
> of a lot of this could be puppetified, granted..
>
>
>
> --
> $ echo "kpfmAdpoofdufevq/dp/vl" | perl -pe
''s/(.)/chr(ord($1)-1)/ge''
>
> --
> 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.
>
>
Hi Andreas,

Deploying with scaling in mind is the best route at onset.
You''ll then be able to load test, debug and evaluate _before_ you reach
the
wall. Which in these days of virtualization can happen between morning and
afternoon.


-- 
Cheers,

Steven
-----------------------
Steven Acres
UNIX/Linux System Administrator

-- 
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 Tue, May 3, 2011 at 3:21 AM, Andreas Kuntzagk
<andreas.kuntzagk@mdc-berlin.de> wrote:
> Hi,
>
> I''m currently using puppet with the buildin server for testing on
a few
> nodes (~5). But in the future my installation will be bigger. It will have
> about 110 nodes of our compute cluster and maybe some additional servers
> (~20).
> Currently I don''t use very complicated manifests and want to
manage only a
> few config files, nfs mounts and the list of installed packages.
>
> But maybe this list will grow with my love for puppet.
> Should I already plan on using a different server? What would you
recommend?
> I will be using apache on one headnode anyway for ganglia & nagios.
> Should I also move puppet to apache? How complicated is this?
> I''m not familar with Ruby or Rails.
Agree with Steven, you should consider apache/passenger:
http://projects.puppetlabs.com/projects/1/wiki/Using_Passenger

On Ubuntu, you can heck if puppet-passenger package is available, and
reference the page above if you have any troubleshooting issues.

Thanks,

Nan

-- 
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.