Folks, I am in the midst of creating a deployment guide for a client that I am working with for the use of Puppet in their environment. The company is big enough that even though the company as a whole uses Puppet already (it's even on the Puppet web site) the local teams I am working with have no knowledge of this.
One of the perennial concerns that has been raised is about scaleability. How many clients can a single Puppet master handle using the following as a baseline: processor0 => Intel(R) Xeon(R) CPU E3-1245 V2 @ 3.40GHz processor1 => Intel(R) Xeon(R) CPU E3-1245 V2 @ 3.40GHz processor2 => Intel(R) Xeon(R) CPU E3-1245 V2 @ 3.40GHz processor3 => Intel(R) Xeon(R) CPU E3-1245 V2 @ 3.40GHz processor4 => Intel(R) Xeon(R) CPU E3-1245 V2 @ 3.40GHz processor5 => Intel(R) Xeon(R) CPU E3-1245 V2 @ 3.40GHz processor6 => Intel(R) Xeon(R) CPU E3-1245 V2 @ 3.40GHz processor7 => Intel(R) Xeon(R) CPU E3-1245 V2 @ 3.40GHz Second: is there a way to use a load balancer in front of a bank of Puppet masters and keep the reports in sync? I am considering proposing Puppet Dashboard as an ENC. That's all I can think of right now but I'll probably have more questions along these lines as I develop my document and strategy. -- Peter L. Berghold [email protected] http://blog.berghold.net -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAArvnv0Bf_7vs9F%3DFU-%2BeHD88moG3H7LcuNhE2ux4qUSHx7N0w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
