Hello Dimitri, On Mon, Sep 7, 2020 at 9:01 AM Chandan kumar <chkumar246@gmail.com> wrote:
Hello,
On Sat, Sep 5, 2020 at 3:44 AM Dimitri Savineau <dsavinea@redhat.com> wrote:
Hi,
We're currently in the progress of using the quay.ceph.io registry [1] with a copy of the ceph container images from docker.io and consumed by the ceph-ansible CI [2].
In TripleO side, daemon:v4.0.12-stable-4.0-nautilus-centos-7-x86_64 is used but this image is not available on quay.io registry <https://quay.ceph.io/repository/ceph-ci/daemon?tab=tags> But v4.0.13-stable-4.0-nautilus-centos-7-x86_64 is available there. Can we get daemon:v4.0.12-stable-4.0-nautilus-centos-7-x86_64 in quay.ceph.io registry? or we switch to v4.0.13-stable-4.0-nautilus-centos-7-x86_64 this tag?
Official ceph images will still be updated on docker.io.
Note that from a ceph-ansible point of view, switching to the quay.ceph.io registry isn't enough to get rid of the docker.io registry when deploying with the Ceph dashboard enabled. The whole monitoring stack (alertmanager, prometheus, grafana and node-exporter) coming with the Ceph dashboard is still using docker.io by default [3][4][5][6].
As an alternative, you can use the official quay registry (quay.io) for altermanager, prometheus and node-exporter images [7] from the prometheus namespace like we're doing in [2].
Only the grafana container image will still be pulled from docker.io.
The app-sre team mirrors the grafana image from docker.io on quay. https://quay.io/repository/app-sre/grafana?tab=tags , we reuse the same in CI?
I have proposed a patch on tripleo-common to switch to quay.io -> https://review.opendev.org/#/c/750119/
Thanks, Chandan Kumar