Hans-Peter Jansen wrote:
Hi,
anybody out there with a working caching scheme for zypper updates/upgrades?
Yes, I actually wrote this up 6-7 years ago, it works very well. The core is a plain squid cache, which a few bits bolted on. http://wiki.jessen.ch/index/How_to_cache_openSUSE_repositories_with_Squid
The problem is two-fold: for one, it needs to intercept https with all kinds of side effects, security implications, etc, and the other is the CDN (mirrorbrain).
Uh, why https:// ?? The mirror system does not support https:// The key issue in caching with squid is that zypper, to speed things up, does segmented downloading. A package will be put together by chunks from multiple mirrors.
What I'm looking for is *not* a complete mirror, because this is overkill for small sites. It would be more in a fashion of a proxy, but should provide the cached packages in a human readable form as well.
What is "a human readable form" to you?
It would proxy zypper fetch requests in a CDN-server agnostic form, fetch the files, as zypper does, and deliver them the "last mile". That way, any (update) package would only be fetched once from upstream, and subsequent accesses are dealt with locally, much improving speed and reducing bandwidth needs.
Yes, that is precisely what I needed too. At the time, I did not have sufficient bandwidth/space to run a mirror, but I wanted a 2nd install or upgrade to run at wire speed. I also did not want the added effort in maintaning a mirror.
Have you guys something up, that (at least partly) works that way? Per?
See above :-) -- Per Jessen, Zürich (13.0°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org