This uses the new zuul-registry container image to run the
intermediate registry. The same authentication data and certs
are used. The new registry also writes to the same swift container,
but uses different pseudo-directories so it won't clash with the
current registry. If there are problems, we can switch back easily.
After successful use of the new registry, we can delete the old data.
Change-Id: Ib855fb99c991411293a617b9b238d79a6bfae328
This ensures that we cleanup images that are superceded and no longer
necessary. We do this to avoid filling the disk with docker images.
Note that we use the -f flag to avoid being prompted by docker image
prune for confirmation.
Change-Id: I8eb5bb97d8c66755e695498707220c9e6e7b2de0
Note, this does not have complete tests yet (we will need to update
the job to start a swift for that).
Change-Id: I2ee7a9e4fb503a3431366c16c380cf09327f6050
This installs a daily cron job for garbage collecting the docker
registry. Note that we need to orphan blobs by deleting their tags for
this to result in any cleaned up blobs. This will be done in a separate
change.
Change-Id: I85c87ee3b3a375e0141ef9b15a0b9e56c0938bd8
This will make sure that the latest relevant images are in the
local image storage, and therefore, will cause docker-compose up
to recreate containers when the images are updated.
Change-Id: Ic6f0bc8c8aea5b5c16501f4ab5d3095fb70c0ff7
Also, correct the host_vars filename. Again.
Also, make sure we run the test on changes to the host_vars filename.
Change-Id: I95fb61531bae677f5c68f4e56ed718da6c507eb9
