A speculative container registry

Go to file

Ian Wienand ce2fb31a72 Fix range response The range starts from zero, so we are returning one byte too many. Docker echos this back to us in the manifest it uploads which is where the extra byte is coming from. This is actually the root cause of the off-by-one error worked around in `134c942835`. A follow-on will clean this up (Ibe061171bfd8ab6043b491bbab933bf277f8e12b). Change-Id: I1fb1abf3c76ea8db7820caa90c97ddbf92997842		2021-09-13 08:23:37 -07:00
playbooks/functional-test	Add a restricted mode (read authentication required)	2021-07-06 17:46:13 -07:00
tests	config: add environment variable substitution	2020-04-13 18:13:26 +00:00
tools	Reject mismatched layer sizes, with some exceptions	2021-09-03 08:50:38 -07:00
zuul_registry	Fix range response	2021-09-13 08:23:37 -07:00
.gitignore	Add README, license, and Zuul config	2019-09-20 09:53:42 -07:00
.gitreview	Added .gitreview	2019-09-19 16:08:44 +00:00
.stestr.conf	Add tox configuration and fixe flake8 errors	2019-10-02 18:05:12 +00:00
.zuul.yaml	Build images on bionic	2021-07-06 17:27:57 -07:00
bindep.txt	Fix container image build	2019-10-02 13:50:42 -04:00
COPYING	Add README, license, and Zuul config	2019-09-20 09:53:42 -07:00
Dockerfile	Bump to python 3.8 base images	2020-05-05 09:24:01 -05:00
README.rst	Add README, license, and Zuul config	2019-09-20 09:53:42 -07:00
requirements.txt	Update pyjwt version to >=2.0.0,<3.0.0	2021-02-01 10:46:09 -08:00
setup.cfg	Fix container image build	2019-10-02 13:50:42 -04:00
setup.py	Initial implementation	2019-10-01 08:09:55 -07:00
test-requirements.txt	Add tox configuration and fixe flake8 errors	2019-10-02 18:05:12 +00:00
tox.ini	Add tox configuration and fixe flake8 errors	2019-10-02 18:05:12 +00:00

README.rst

Zuul Registry

This is a container image registry for use with the Zuul project gating system.

The defining feature of this registry is support for shadowing images: it allows you to upload a local version of an image to use instead of an upstream version. If you pull an image from this registry, it will provide the local version if it exists, or the upstream if it does not.

This makes it suitable for use in a Zuul-driven speculative image pipeline.

The latest documentation for Zuul is published at: https://zuul-ci.org/docs/

Getting Help

There are two Zuul-related mailing lists:

zuul-announce: A low-traffic announcement-only list to which every Zuul operator or power-user should subscribe.
zuul-discuss: General discussion about Zuul, including questions about how to use it, and future development.

You will also find Zuul developers in the #zuul channel on Freenode IRC.

Contributing

To browse the latest code, see: https://opendev.org/zuul/zuul-registry To clone the latest code, use git clone https://opendev.org/zuul/zuul-registry

Bugs are handled at: https://storyboard.openstack.org/#!/project/zuul/zuul-registry

Suspected security vulnerabilities are most appreciated if first reported privately following any of the supported mechanisms described at https://zuul-ci.org/docs/zuul/user/vulnerabilities.html

Code reviews are handled by gerrit at https://review.opendev.org

After creating a Gerrit account, use git review to submit patches. Example:

# Do your commits
$ git review
# Enter your username if prompted

Join #zuul on Freenode to discuss development or usage.

License

Zuul-registry is free software licensed under the General Public License, version 3.0.

Python Version Support

Zuul requires Python 3. It does not support Python 2.