Hey Wes,
stupid question: what about the molecule tests? Since they are running
within containers (centos-8, centos-7, maybe/probably ubi8 soon), we
might hit some limitations there.... Unless we're NOT using docker.io
already?
Cheers,
OK.. so easy answer
2. any content ci uses from
docker.io will be mirrored in quay and the rdo registry including base images.
So I would switch the molecule / tox config to use quay as soon as we have images there.
I'm searching around for that code in tripleo-ansible and validations and it's not where I thought it was.
Do you have pointers to where
docker.io is configured.
Thanks
C.
On 9/2/20 1:54 PM, Wesley Hayutin wrote:
> Greetings,
>
> Some of you have contacted me regarding the recent news regarding
> docker.io <http://docker.io>'s new policy with regards to container pull
> rate limiting [1]. I wanted to take the opportunity to further
> socialize our plan that will completely remove docker.io
> <http://docker.io> from our upstream workflows and avoid any rate
> limiting issues.
>
> We will continue to upload containers to docker.io <http://docker.io>
> for some time so that individuals and the community can access the
> containers. We will also start exploring other registries like quay and
> newly announced github container registry. These other public registries
> will NOT be used in our upstream jobs and will only serve the
> communities individual contributors.
>
> Our test jobs have been successful and patches are starting to merge to
> convert our upstream jobs and remove docker.io <http://docker.io> from
> our upstream workflow. [2].
>
> Standalone and multinode jobs are working quite well. We are doing some
> design work around branchful, update/upgrade jobs at this time.
>
> Thanks 0/
>
>
> [1] https://hackmd.io/ermQSlQ-Q-mDtZkNN2oihQ
> [2] https://review.opendev.org/#/q/topic:new-ci-job+(status:open+OR+status:merged)
--
Cédric Jeanneret (He/Him/His)
Sr. Software Engineer - OpenStack Platform
Deployment Framework TC
Red Hat EMEA
https://www.redhat.com/