Ansible role that installs and configures a variety of caching proxies and artifact hosting web services.
Based on the Docker Global Hack Day entry, Snakes on a Plane which was unfortunately never completed.
- When you have no Internet connectivity or are operating with bandwidth and availability constraints, ex: On a plane or on a poor VPN connection.
- When your organization has remote offices/employees whose productivity would benefit from having fast local copies of large binaries like ISOs, OVAs, or OS packages.
- When your dev process depends on external dependencies from services that are susceptible to outages, ex. NPM or PyPI.
- When your dev process depends on third-party artifacts that are pinned to certain versions and you want a local copy of those pinned dependencies in case they become unavailable in the future.
Installs the following services as server blocks (aka. virtual hosts) behind a front-end nginx web server:
- apt-cacher-ng: A caching proxy tailored to cache operating system packages for Debian-based distributions
- devpi: A PyPI mirror that is also capable of acting as a private PyPI index for uploading of custom Python packages
- docker registry v2: A private Docker registry
- nginx HTTP caching proxy: A general purpose HTTP caching proxy.
- sinopia: An https://www.npmjs.com caching proxy.
- Tested on Ansible 1.8
- A working installation of Docker. angstwad.docker_ubuntu is a great Ansible role for this, but is not a declared dependency of this role in the interest of not making this role overly opinionated.
- jdauphant.nginx (Galaxy/ GitHub)
apt_cache_server_enable: true
apt_cache_server_dir: /var/cache/apt-cacher-ng
apt_cache_server_port: 3142
apt_cache_server_vhost_name: "apt-cache apt-cache.yourdomain.local"
devpi_server_enable: true
devpi_server_dir: /opt/devpi-server
devpi_server_port: 3141
# password for the root user
devpi_server_password: 1234
devpi_server_vhost_name: "devpi devpi.yourdomain.local"
docker_registry_enable: true
docker_registry_dir: /opt/docker-registry
docker_registry_port: 5000
docker_registry_vhost_name: "registry registry.yourdomain.local"
nginx_caching_proxy_server_enable: true
nginx_caching_proxy_server_dir: /var/cache/nginx
# Port 1080 is the default for the SOCKS service
nginx_caching_proxy_server_port: 1080
nginx_caching_proxy_server_inactive: 3d
# "resolver" defaults to Google's DNS. If you want to cache private
# intranet resources, then you should set this to an internal DNS server.
nginx_caching_proxy_server_resolver: 8.8.8.8
# Max cache size on disk
nginx_caching_proxy_server_max_size: 100g
nginx_caching_proxy_server_proxy_cache_valid_codes: 200 301 302
nginx_caching_proxy_server_proxy_cache_valid_time: 3d
nginx_caching_proxy_server_vhost_name: "proxy proxy.yourdomain.local"
npmjs_server_enable: true
npmjs_server_dir: /opt/npmjs-server
npmjs_server_port: 4873
npmjs_server_vhost_name: "npm npm.yourdomain.local"
yum_repo_enable: true
yum_repo_dir: /opt/yum-repo
yum_repo_server_port: 80
yum_repo_vhost_name: "yum yum.yourdomain.local"The easiest way to use the Apt caching proxy is to put a line like the following
into a file like /etc/apt/apt.conf.d/02proxy:
Acquire::http { Proxy "http://CacheServerIp:3142"; };
More details at: https://www.unix-ag.uni-kl.de/~bloch/acng/html/config-servquick.html#config-client
See tutorials at: http://doc.devpi.net/latest/
See documentation at: https://github.com/docker/distribution
Set your OS's HTTP proxy to be the caching proxy's virtual host. Details are specific to your OS.
Useful information from the HTTP caching proxy can be found in custom headers in the HTTP response. Ex:
# Interesting headers in HTTP responses
# ===
X-Cache-Status: MISS # Indicates a cache miss
X-Cache-Status: HIT # Indicates a cache hit
# The cache can be bypassed and re-populated by setting the custom header
# "X-Refresh: true" in the originating HTTP request
X-Cache-Status: BYPASS
# Items may be programmatically purged from the cache by performing
# a GET on the "/purge" location. Ex:
# Remove the file from the disk cache by hitting the "/purge" location
curl -sD - http://localhost:1080/purge/releases.ubuntu.com/14.04/ubuntu-14.04-server-amd64.template
...
HTTP/1.1 200 OK
See implementation details at: https://hub.docker.com/r/rnbwd/sinopia/
This role sets up a virtual host with directory indexing to serve a RPM/YUM repo.
In order to populate the RPM/YUM repo, first copy your RPMs to yum_repo_dir.
Then run createrepo on that directory to create the repo meta-data files.
The createrepo command needs to be re-run every time an RPM is added or
removed from the repo in order to update the repo's metadata.
The createrepo command can be obtained either by installing the OS package
for createrepo, or by utilizing the
sark/createrepo Docker
container. Ex:
$ docker run -e verbose=true -v /opt/yum-repo:/data sark/createrepo:latest
Spawning worker 0 with 1 pkgs
Worker 0: reading apache-2.4.10-15.mga5.i586.rpm
Workers Finished
Saving Primary metadata
Saving file lists metadata
Saving other metadata
Generating sqlite DBs
Starting other db creation: Wed Apr 29 18:20:12 2015
Ending other db creation: Wed Apr 29 18:20:12 2015
Starting filelists db creation: Wed Apr 29 18:20:12 2015
Ending filelists db creation: Wed Apr 29 18:20:12 2015
Starting primary db creation: Wed Apr 29 18:20:12 2015
Ending primary db creation: Wed Apr 29 18:20:12 2015
Sqlite DBs complete
$ find /opt/yum-repo
/opt/yum-repo/
/opt/yum-repo/apache-2.4.10-15.mga5.i586.rpm
/opt/yum-repo/repodata
/opt/yum-repo/repodata/cd586a4b60edfe907679da9dd1012a2511f76ee7379c0e8b43a278259c683c7f-filelists.sqlite.bz2
/opt/yum-repo/repodata/48cdb06866f310abc4792dd9e21114bc2498bd58842436bb81a96bd5fa3855eb-other.sqlite.bz2
/opt/yum-repo/repodata/repomd.xml
/opt/yum-repo/repodata/f2d3501c6881b38b1ccbe8735d7e6203e1642a4bd8795c39758afdf6a4555f4f-filelists.xml.gz
/opt/yum-repo/repodata/5d0ee9e4bc83b6ca745030e0fbc064c096339f0612103ab8b4bef1e43964fb4a-other.xml.gz
/opt/yum-repo/repodata/0a185843f7f2f9df9e305650ed4068202ccc8a476f1b5ecb3d79c1580fd1cfee-primary.sqlite.bz2
/opt/yum-repo/repodata/92277e8225a8f1f3e5ed2171031a25400ca283b290428138c1b2336b144db493-primary.xml.gz
Statistics from the front-end server are available through the "/_status" location. Ex:
$ curl -s http://localhost:8080/_status
Active connections: 1
server accepts handled requests
28 28 28
Reading: 0 Writing: 1 Waiting: 0
This can be used to gather web server statistics using an application like collectd.
Apache License 2.0
- The folks who conceived the Snakes on a Plane Docker Hack Day project.
- The Engineering Team at VMware, who proved this idea out by implementing a similar set of caching proxy servers for their global remote offices in order to improve developer productivity.
Are welcome.