We want to use stop_grace_period to manage gerrit service stops. This
feature was added in docker-compose 1.10 but the distro provides 1.5.
Work around this by installing docker-compose from pypi.
This seems like a useful feature and we want to manage docker-compose
the same way globally so move docker-compose installation into the
install-docker role.
New docker-compose has slightly different output that we must check for
in the gitea start/stop machinery. We also need to check for different
container name formatting in our test cases. We should pause here and
consider if this has any upgrade implications for our existing services.
Change-Id: Ia8249a2b84a2ef167ee4ffd66d7a7e7cff8e21fb
This adds a new handler to restart the zuul registry to pick up the new
cert. We may want to consider updating zuul registry to accept a reload
of ssl config without restarting the service.
Depends-On: https://review.opendev.org/702050
Change-Id: I23f6bea68285bc7cb0d12224235eaa16f0d07986
To make it clear that docker hub is but one of many possible registries,
update our usage of FROM and image: lines to include docker.io in the
path.
There are a few other FROM lines for the gitea images which are handled
in a separate stack.
Change-Id: I6fafd5f659ad19de6951574afc9a6b6a4cf184df
Just to eliminate the possibility that a bug in this may be causing
us to erroneously delete blobs.
Change-Id: I048d9ae5ba92984c90f84f231b412050a52fcea6
This is no longer used as read access is provided to unathenticated
users with the recently added JWT support.
Depends-On: https://review.opendev.org/687422
Change-Id: I36fd28710c644be9b07d645c6b0c6092f52a7385
An upcoming change will add JWT authentication to the registry;
prepare for that by establishing a server-side secret for use
in signing the tokens.
Change-Id: Ibaa15dd0c4b0d797f01a1886186fdc021dc990fa
We're trying to get clouds.yaml into /etc/openstack/clouds.yaml.
This should accomplish that. The previous configuration was in
error and wiped out the /etc directory which made things not work
well.
Change-Id: I88e69b05f3e8c1688d24736fa775163fc25a07f0
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
