OpenStack Block Storage (Cinder) Specifications
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Brian Rosmaita 5af1702456 Add victoria directory for specs 2 weeks ago
doc Add victoria directory for specs 2 weeks ago
specs Add victoria directory for specs 2 weeks ago
.gitignore Adds Block Storage v2 API specification information 5 years ago
.gitreview OpenDev Migration Patch 10 months ago
.testr.conf Initialize the Cinder-Specs Repository 5 years ago
.zuul.yaml import zuul job settings from project-config 1 year ago
LICENSE Initialize the Cinder-Specs Repository 5 years ago
README.rst Update url of the cinder-specs's document 2 years ago
bindep.txt Update bindep.txt for doc builds 2 years ago
setup.cfg Change openstack-dev to openstack-discuss 1 year ago Fix rst formatting and fix tox 5 years ago
test-requirements.txt Retarget specs to ussuri 1 month ago
tox.ini Retarget specs to ussuri 1 month ago


Team and repository tags


OpenStack Cinder Specifications

This git repository is used to hold approved design specifications for additions to the Cinder 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 layout of this repository is:


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

Specifications are proposed for a given release by adding them to the specs/<release> 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.

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.