Rather Openstack-Helm specific. Yes, they are already published. I see what you mean. Airshipit is just an account on quay.io. docker.io/openstackhelm is another account. There is no problem publishing images to any other quay account (Openstack specific). On Sun, Jan 26, 2025 at 10:48 AM Doug Goldstein <cardoe@cardoe.com> wrote:

So will OpenStack specific containers be published to quay.io/airshipit/ ? -- Doug

On Jan 16, 2025, at 10:06 AM, Vladimir Kozhukalov <kozhukalov@gmail.com> wrote:

 Hi,

This is to announce multiple things:

1) OpenStack/Loci (a project for building OpenStack images) is currently equipped with periodic jobs that are run nightly.

These jobs build images for 3 most recent OpenStack releases: - 2023.2 Bobcat - 2024.1 Caracal - 2024.2 Dalmatian

Images are published to these two destinations: - docker.io/loci/* (which is known for its strict request rate limits) - quay.io/airshipit/* (which is much more tolerant to the number of requests)

Images are tested before publishing with two basic deployment configurations: - compute-kit (Deploy minimal set of OpenStack components to run VMs) - cinder (Deploy Cinder with Ceph backend)

2) By default we are going to use Loci images published to the Quay registry [1]. All test jobs will be run with these images and this is also a recommendation for users to consume images from quay to mitigate possible rate limit issues.

3) OpenStack/OpenStack-Helm-Images project will build only non-OpenStack images. Primarily the motivation is to deduplicate the code base. Consequently, OpenStack images published nightly to docker.io/openstackhelm/* will not be updated after 2024.2.

[1] https://review.opendev.org/c/openstack/openstack-helm/+/939426

-- Best regards, Kozhukalov Vladimir

-- Best regards, Kozhukalov Vladimir