OpenStack Image Management (Glance) Specifications
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Rajat Dhasmana a5bcf0c19a Update new location APIs spec
The update is based on the review comments[1] on the implementation
patch and IRC discussion[2].


Change-Id: I635b19a1356fb685c3c814a12707592034ee0ffc
2 days ago
doc Add 2023.2 directory for specs 3 months ago
priorities Add 2023.2 directory for specs 3 months ago
scripts Add a script to prepare the next cycle 2 months ago
specs Update new location APIs spec 2 days ago
tests Remove reviewers section from template 7 years ago
.gitignore Switch to stestr 5 years ago
.gitreview OpenDev Migration Patch 4 years ago
.stestr.conf Switch to stestr 5 years ago
.zuul.yaml [ussuri][goal] Drop python 2.7 support 3 years ago
LICENSE Add base glance-specs framework 9 years ago
README.rst Add a script to prepare the next cycle 2 months ago
bindep.txt [ussuri][goal] Drop python 2.7 support 3 years ago
requirements.txt Switch to newer openstackdocstheme version 3 years ago
tox.ini Add a script to prepare the next cycle 2 months ago


Team and repository tags

The following tags have been asserted for the Glance Specifications
Follow the link for an explanation of these tags.

OpenStack Glance Specifications

This git repository is used to hold approved design specifications for additions to the Glance project. Reviews of the specs are done in gerrit, using a similar workflow to how we review and merge changes to the code itself.

The general layout of this repository is:


You can find an example spec in specs/template.rst.

Beginning with the Mitaka release, there is a further subdivision into:


A specification is proposed for a given release by adding it to the specs/<release>/approved directory and posting it for review. The implementation status of a blueprint for a given release can be found by looking at the blueprint in launchpad. Not all approved blueprints will get fully implemented.

When a feature has been completed, its specification will be moved to the 'implemented' directory for the release in which it was implemented.

Specifications have to be re-proposed for every release. The review may be quick, but even if something was previously approved, it should be re-reviewed to make sure it still makes sense as written.

Prior to the Juno development cycle, this repository was not used for spec reviews. Reviews prior to Juno were completed entirely through Launchpad blueprints:

Please note, Launchpad blueprints are still used for tracking the current status of blueprints. For more information, see:

For more information about working with gerrit, see:

To validate that the specification is syntactically correct (i.e. get more confidence in the Jenkins result), please execute the following command:

$ tox

After running tox, the documentation will be available for viewing in HTML format in the doc/build/ directory. Please do not checkin the generated HTML files as a part of your commit.

At the start of a new cycle, the right files and directories can be created and modified using the following command:

$ tox -eprepare-next-cycle <cycle>

For instance:

$ tox -eprepare-next-cycle 2023.2

The changes should then be reviewed and committed manually.