Access to apt.puppetlabs.com slow for some IP addresses

[Johannes Grassler]

Hello,

we are currently creating and tearing down lots of VMs in our lab environment. This includes retrieving and installing Puppet from the Puppetlabs repository at apt.puppetlabs.com. Recently we found that from some addresses in our lab's /24 access to http://apt.puppetlabs.com is painfully slow (things are trickling in at ~800 bytes per second). We double-checked our lab network and the automated VM provisioning process and found nothing amiss. Now we are wondering whether we ran into some kind of rate limiting on the repository's side, since we do repeatedly retrieve the same packages in the course of VM provisioning, more often than not from the same IP address. One of the 'slow' addresses in question is 37.44.0.243. Is there anyone on this list who could look into this?

If we are indeed causing too much load we'd be happy to set up a public mirror of apt.puppetlabs.com.

Cheers,

Johannes

-- 
SysEleven GmbH
Umspannwerk - Aufgang C
Ohlauer Straße 43
10999 Berlin

Tel +49 30 233 2012 0
Fax +49 30 616 755 50

http://www.syseleven.de
http://www.facebook.com/SysEleven

Firmensitz: Berlin
Registergericht: AG Berlin Charlottenburg, HRB 108571 B
Geschäftsführer: Marc Korthaus, Thomas Lohner

[Matthaus Owens]

Johannes,

I don't see anything on our end that would be causing the issue you're
seeing. I have enabled some additional logging on the apt repos to get
us extra information about what might be going on. I have also opened
a ticket https://tickets.puppetlabs.com/browse/CPR-60 to track this
issue. Please feel free to add any additional information that might
help us diagnose the problem. Thanks!

> --
> 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 puppet-users...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/a289bd73-cddf-4b76-80d1-c5e5ee6f30d5%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



--
Matthaus Owens
Puppet Labs

Join us at PuppetConf 2014, September 20-24 in San Francisco
Register by September 8th to take advantage of the Final Countdown —save $149!

[Andreas Ntaflos]

On 2014-08-06 11:11, Johannes Grassler wrote:
> Hello,
>
> we are currently creating and tearing down lots of VMs in our lab
> environment. This includes retrieving and installing Puppet from the
> Puppetlabs repository at apt.puppetlabs.com.

Not an answer to your question directly, but for lab environments (or
any kind of environment, really) it is probably a good idea to set up an
APT cacher or some other kind of APT forward proxy. This will certainly
speed up package downloads on your lab machines and the impact on the
upstream repositories will be minimised.

We run Apache Trafficserver as a forward proxy but there are other
options, such as squid-deb-proxy which is probably what I'd use in a new
lab environment. Easier to run than a real mirror and usually requires
almost no maintenance at all.

Andreas

[Johannes Grassler]

Hello,

thanks for confirming there's nothing wrong on the apt.puppetlabs.com side! That leaves our testbed's networking setup as the most likely culprit then.

Either way, we'll set up a caching proxy to reduce the load we are causing on upstream repositories now.

Cheers,

Johannes