Several options exist for setting up a local mirror or cache of the Ubuntu archives (apt-mirror, debmirror, apt-cacher-ng, apt-proxy, approx...) but none of them is fully supported in main. Any site with more than 2 Ubuntu machines is likely to set up one of those, we should investigate options, promote to main and support the relevant one(s).

Release Note



Having a recommended way to solve the mirror problem is useful for a lot of sysadmins that looks for a solution to this problem.

User stories

Karl is a sysadmin in a small office with 10 ubuntu machines. He wants to avoid wasting bandwidth for the clients that update and sets up a local proxy solution for this.


There are three areas that need investigation. Simple caching that should cover most cases when people are looking for bandwidth saving. A full/partial mirror that is useful only for a smaller subset of people. And finally repository management that is out of scope for this document.

Cache solutions

During the session people expressed concerns about all the available cache solutions with the exceptions for squid. Given that squid is already in main we should provide a squid configuration that is geared towards the deb caching use case. The biggest obstacle people had was the squid.conf file.

Action items for caching:

Mirror solutions

The discussion on mirror solutions was inconclusive. Only rsync was approved by everyone, but its not useful for partial mirroring and complicated to use (lots of switches):

Action items for mirroring:

Repo managment solutions

Action items for repository managment:

Releated work

A more complete spec that also requires much more code:

BoF agenda and discussion

Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.


FoundationsTeam/Specs/LucidLocalRepoSupport (last edited 2010-02-26 18:13:39 by ceg)