On 10/05/2010 5:16 PM, Daniel Pittman wrote:
Nicolas Szalay<nsza...@qualigaz.com> writes:
Le jeudi 06 mai 2010 à 13:49 -0700, Thomas von Steiger a écrit :
I think about whats the best solution to have puppet-proxys for
systems without direct connection to the puppetmaster.
- Route all the trafic with iptable forwarding to one puppetmaster.
- Build puppetmaster-proxy vm's installed from a puppetmaster.
- Using http-proxy services.
Are there any experience or best practices for systems with indirect
access to a puppetmaster?
You can setup a nginx (or apache) as a front-end and then forward
requests to upstream server(s).
Since we are starting to feel the pinch of traffic levels from running two
sites over a WAN link with a single puppetmaster:
Does this actually get any benefit of caching on the client, or would we need
to deploy a second puppetmaster server to achieve that?
Daniel
Daniel,
Take a look at http://projects.puppetlabs.com/issues/3408 to help out
with your WAN bandwidth issues.
Ben
--
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.
