[LRUG] Vagrant, Puppet and Linode

[Gareth Humphries]

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
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20130425/20dfed2f/attachment-0003.html>