On Mon, 9 Jan 2023 at 22:10, Clark Boylan <cboylan@sapwetik.org> wrote:
On Mon, Jan 9, 2023, at 10:02 AM, Radosław Piliszek wrote:
Hi OpenDevers,
Are there any plans to have a container registry at OpenDev? Is there any thread that could be followed?
We've had several depending on how you look at it for quite some time now. There are the caching proxies for quay and docker hub. There is the insecure CI registry used for intermediate image artifacts. And there are buildset registries that live for the lifetime of a buildset providing locally cached images for jobs within a buildset.
You will probably need to be more specific about what you are asking for.
Yeah, my bad. I obviously had it in mind when writing. ;-) I meant a permanent, publicly-available-for-download storage of versioned container images.
On Tue, 2023-01-10 at 10:28 +0100, Radosław Piliszek wrote: packaging of openstack has generally been out of scope fo the foundation. while there are some spec file repose that are hostsed as part of opendev binary packanges like rpms and debs have generally been considerd out of scope. the ci obvioulsy does produce tarballs of the distirbution and we push to pypi when appropriate but contaienr images has previously not been a artifact generated by opendev or openstack. on the openstack side thats partly because there are 3 compteing container image project for openstack that i am aware of. kolla, loci and the zull project provided a third way to build images. while i agree that it might be nice for openinfra to provide a generic registry instance similar to the one provide by github for integration with there ci i would be concerned by how much load that registry would have and the resocues both human and machine that would be required to run it.
Unless you somehow omitted that one option from your answer, I think you have answered that it is not supported at the moment which would agree with my upfront knowledge. On that note, are there any plans to add that support? Or is the best recommendation to use Quay (as DockerHub's limits are hurtful).
it would certenly be nice to have a opendev quay instance or similar registry aviable that would not not have the same rate limits. kolla if i am not mistaken has mostly swapped to quay.io as has tripleo/rdo due to the dockerhub limits. if we had an opendev registry we would still proably want to keep the iamge mirror to other registries. having the ablity to provide a contaienr registry like the github contaiern registry would bring more parity to the opendev hosting plathform vs github. had you a partical usage model in mind? i.e. a post merge job that woudl push on each commit or a perodic that woudl push some iamge nightly which would be enabled by the reslevent projects? which registry would be the athoritive default source and which would be the mirror? opendev? quay? dockerhub? the other question i woudl have is would the registry be open to project not hosted on opendev for development? presumably not but im just trying to gague how you expect it to be used.