I'm on the extremely small scale end from what has been previously described, but this could prove useful to those who want to manage a small number of hosts and are curious how little they need to run Puppet. I've just begun using Puppet, and so only have 10 hosts right now, but here's what I'm running...
CentOS 5.6 x64 VMware ESXi virtual machine - 512MB RAM - 1 x 2.33GHz CPU - Paravirtual Roles are... - Puppetmaster - puppet-dashboard w/ mysql & apache + passanger - local yum repo over http - OSSEC server. - Trey According to zabbix my system averages about .20 CPU load over 15 minute average. I occassionally peak 1.0 but that's typically when I'm running puppet manually very rapidly during testing. Memory usage is about 70% on average. On May 11, 12:41 am, Matthew Marlowe <m...@deploylinux.net> wrote: > Keep in mind that there are many ways to run puppet. > > We manage ~100 nodes with just a single puppet master running within a gentoo > VM w/ only single cpu core and 2GB ram. Catalog compile times average under > 0.6 seconds. This is also w/ web brick. The puppet master VM also serves as > a master nfs server and gentoo build server. > > Thats a lot of stuff on a single small VM, but it works perfectly for us > because: > a) our default puppet run interval is 4hrs (if something goes wrong w/ one of > our manifests or the server, we'll probably notice it and stop it before too > many servers get updated - for our purposes, we don't see any benefit to using > an interval less than 4hrs. 4hrs is certainly sufficient for most common > security updates and we also do not want to have normal updates impacting > production performance during peak business hours - so 25% of servers updating > every hour is perfect for us. ). > b) Many of our servers, mostly the gentoo ones, only execute puppet when > puppetrun is invoked either manually by systems administrators for the > specific nodes they are reconfiguring or automatically as part of a nightly > update systems maintenance cron job). > > Basically, puppet is extremely flexible w/ hardware, and it is likely your own > preferences and production requirements will dictate the hardware needed > rather than puppet itself. > > On Tuesday, May 10, 2011 06:04:22 am Panaman wrote: > > > I've been messing around with Puppet on a VM on my personal desktop. > > It looks descent. I was wondering what kind of load this thing would > > have managing about 400 nodes. > > Does this thing require a beefy server? > > Matt > -- > Matthew Marlowe / 858-400-7430 / DeployLinux Consulting, Inc > Professional Linux Hosting and Systems Administration Services > www.deploylinux.net * m...@deploylinux.net > 'MattM' @ irc.freenode.net -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
