[tripleo] docker.io rate limiting

Wesley Hayutin whayutin at redhat.com
Wed Sep 2 11:54:29 UTC 2020


Greetings,

Some of you have contacted me regarding the recent news regarding 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 from our upstream workflows and avoid any rate limiting
issues.

We will continue to upload containers to 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 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)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20200902/55500bd6/attachment.html>


More information about the openstack-discuss mailing list