[LRUG] Vagrant, Puppet and Linode

[Gareth Humphries]

Greetings!

Yes, I still lurk here - despite being neither in London nor a Ruby User
(or a Group, for that matter) - as there are plenty of non-ruby discussions
I can learn from.

I normally keep quiet, but couldn't bite my tongue on this one; it sounds
like you were running your master using webrick, which is what it uses by
default as a webserver, and suitable for testing purposes or running, say,
40-50 nodes.  Use apache + passenger instead to get all the same benefits
you would get when running rails out of passenger instead of instantiating
a new ruby for each request (I believe i did this at a former workplace of
ours, and got a 200x performance improvement).

>From memory, it was 'sudo apt-get install puppet-master-passenger', and
editing a yaml file or two.  I'll check my puppet::master manifest and let
you know.

If you still hit scaling issues, you can put multiple masters behind a load
balancer just fine, and scale up that way.  In fact, that's a good idea for
the reasons you all already know anyway...

On the speed front, well, puppet client IS slow, but there's no need for
the master to be holding you back.  Version 3 is big improvement too - 40%
- 60% faster, and nicenesses like hiera included in base and sensible
scoping etc.


G2

PS - Stick with cron (minute => fqdn_rand(60) ) & 'puppet agent
--onetime'.  Agent as a daemon eats too many rams.



> Hey, G2!
>
> Our experience using a puppet master was very different. We found that,
> after 50 or 60 nodes, the puppet master became a significant bottleneck.
> So, we switched to just having the puppet code in a git repo and checking
> it out onto the servers.
>
> That was quite a while ago though, so maybe the issue we were having has
> been fixed in a more recent version of puppet.
>
> David
>
>
>
> On 24 April 2013 16:39, Gareth Humphries <gareth1 at erozen.org> wrote:
>
> > If you have more than a few servers, please use a puppet master - less
> > resource drain on hosts, faster rollout of changes, and you gain exported
> > resources which open all sorts of doors you never knew existed. I run a
> 200
> > and something node domain off a master with 2x2Ghz 4Gb, and it's not
> > taxed.  It's worth it.
> >
> > For those interested, we have ec2 'stem cell' ami's, which contain the
> > bare minimum to provision a new host (basically consists of an init
> script
> > to build puppet.conf and run puppet on boot). We use the userdata to
> define
> > what should be applied to new instances on boot. Works a treat.
> >
> >
> > Gareth.
> >
> >
> > You generally run puppet as root. Nothing in staging or production
> >> references anything to do with vagrant. Our vagrant projects reference
> the
> >> Puppet git repo.
> >>
> >>
> >> >
> >> > Would you be willing to send me your bootstrap script? I think more
> than
> >> > anything that's what will help all the pieces fall in place in my
> mind.
> >> > I'll probably need to write my own, but to have yours to work off of
> (I
> >> > learn by studying examples) would be very helpful.
> >> >
> >>
> >> It's got some bits that I can't publish, but these are the crucial
> parts;
> >>
> >> This installs puppet 2.7.3 on a fresh Ubuntu 12.04 server.
> >>
> >> apt-get update && apt-get -y install git-core ruby facter && \
> >> wget http://www.puppetlabs.com/downloads/puppet/puppet-2.7.3.tar.gz &&
> \
> >> tar xvf puppet-2.7.3.tar.gz && \
> >> cd /root/puppet-2.7.3 && ruby install.rb
> >>
> >> This is how you apply a checked out working copy of a puppet repo. Your
> >> structure might vary, but the differences should be pretty obvious.
> >>
> >> puppet apply --modulepath=/tmp/puppet/modules
> >> /tmp/puppet/manifests/site.pp
> >>
> >>
> >> Have fun
> >>
> >>
> >>
> > _______________________________________________
> > Chat mailing list
> > Chat at lists.lrug.org
> > http://lists.lrug.org/listinfo.cgi/chat-lrug.org
> >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20130424/1684d212/attachment.htm
> >
>
> ------------------------------
>
> _______________________________________________
> Chat mailing list
> Chat at lists.lrug.org
> http://lists.lrug.org/listinfo.cgi/chat-lrug.org
>
>
> End of Chat Digest, Vol 87, Issue 39
> ************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20130425/4bf9a2d9/attachment.html>