On Tue, 18 Jun 2019, Ken Dreyer wrote:
On Tue, Jun 18, 2019 at 9:09 AM Sage Weil <sweil@redhat.com> wrote:
On Tue, 18 Jun 2019, David Galloway wrote:
What's the status of registry.ceph.com? Has it been abandoned? Can we repurpose or kill it? It's currently in OVH's cloud (not Sepia). We can host a container registry (publicly) in the Sepia lab no problem.
Not sure.. dan, was this something you set up long ago?
I think I set that up a while back. It's definitely abandoned when I found out the pain this would involve to do things like updates, authentication, and sane garbage collection.
In RH we have a few internal OpenShift instances for CI, and they prune all images older than two weeks. The command that the administrators run is:
oc adm prune images --keep-tag-revisions=2 --keep-younger-than=720h --registry-url=docker-registry-default.cloud.registry.example.com --confirm
They probably run that in cron or something.
That doesn't look or sounds that bad...
*However*, please take my advice as someone who has tried to operationalize my own registry in my spare time and failed: quay.io has pretty good garbage collection now. Eg. they prune an old image immediately once you delete or move the repository's tag. Red Hat is planning to use quay.io for more and more things, so it needs to scale.
I'm not sure I read this paragraph correctly. Are you saying we should use quay? Or that garbage collection is hard in general? Because I think the single oc adm prune command above is all that we need... we'll be publishing a zillion ci-built containers and trim them after 2 weeks. What's missing? sage