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