OpenStack Image Management (Glance) Specifications
Go to file
Nguyen Hung Phuong 79b27e6502 fix tox python3 overrides
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.

We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.

We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.

Change-Id: I225b740cd85207e2785ab60ba7e626a773617b0c
2018-07-03 11:52:06 +07:00
doc Introduce db sync check feature 2018-03-09 12:23:24 +05:30
priorities Add release dates to Rocky priorities page 2018-03-26 19:10:19 -04:00
specs Merge "Add spec to mitigate OSSN-0075" 2018-06-07 20:24:20 +00:00
tests Remove reviewers section from template 2016-05-13 15:37:10 -05:00
.gitignore Adds Image service v1 and v2 specification info in general 2014-12-05 16:50:39 -06:00
.gitreview Added .gitreview 2014-05-08 19:05:52 +00:00
.testr.conf Add base glance-specs framework 2014-05-28 17:20:37 -07:00
LICENSE Add base glance-specs framework 2014-05-28 17:20:37 -07:00
README.rst Add alt text for badges 2016-12-01 11:56:10 -05:00
requirements.txt add whereto for testing redirects 2017-12-02 17:13:38 +00:00
setup.cfg Update glance-specs to use openstackdocstheme 2017-11-28 14:19:44 -05:00 Add base glance-specs framework 2014-05-28 17:20:37 -07:00
tox.ini fix tox python3 overrides 2018-07-03 11:52:06 +07:00


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.