I am currently using passenger and puppet 0.25.5 on RHEL 5.4 I am looking to support 3000 - 4000 nodes in the up coming years. 2000 nodes in one data center 500 nodes in each of three more data centers (1500 nodes)
The first use of puppet will be to allow us to fully provision a RHEL server. We are planning on using RPM packages via YUM to install most files. Configuration files / changes will be managed via puppet. Right now about 70% static files and 30% templates. There are not currently any recursive file copies. We have about 20 modules for configuring servers for our first application area that is going to make use of puppet. We expect this to get quite a bit larger over the next year. I also expect to develop another 10 - 20 modules for base operating system configuration. I am currently worried about scalability as the number of modules and clients on my puppet server increases. I am planning on locating at least one puppet server in each of the 4 data centers. I am not finding any information on what to expect and to design into my infrastructure as it matures so I don't run into any unexpected surprises. It sounds like some people are using puppet in large environments and I would like to know what the issues that have been run into and if there is a way to design the environment to avoid these issues. I have been reading through the puppet mailing lists, wiki, and documentation which has gotten me to my current use of apache/passenger. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
