OpenStack Block Storage (Cinder) Specifications

Go to file

xing-yang cbf79f0543 Differentiate thick and thin provisioning If a driver reports thin_provisioning_support to True and thick_provisioning_support to True on a pool that can support both thin and thick volumes, and the user wants to create a thick volume, the current logic in the scheduler would use the wrong logic which makes decisions based on provisioned_capacity_gb and max_over_subscription_ratio. This spec proposes a solution to address the problem. Change-Id: I9d78ee92fac962f69b56a7bc149ee113c1b18b3f Implements: blueprint differentiate-thick-thin-in-scheduler		2016-06-30 05:04:52 -04:00
doc/source	Remove Tempest reference in conf.py	2016-05-13 11:09:00 +02:00
specs	Differentiate thick and thin provisioning	2016-06-30 05:04:52 -04:00
tests	Remove hardcoded releases list from unit tests	2015-10-05 23:31:43 +03:00
.gitignore	Adds Block Storage v2 API specification information	2014-10-17 20:30:44 -05:00
.gitreview	Added .gitreview	2014-05-09 22:05:53 +00:00
.testr.conf	Initialize the Cinder-Specs Repository	2014-05-20 19:37:21 -06:00
LICENSE	Initialize the Cinder-Specs Repository	2014-05-20 19:37:21 -06:00
README.rst	Workflow documentation is now in infra-manual	2014-12-05 03:30:36 +00:00
requirements.txt	Merge "Remove docutils pin"	2014-10-26 18:24:08 +00:00
setup.cfg	Merge "remove python 2.6 trove classifier"	2016-02-24 17:56:05 +00:00
setup.py	Fix rst formatting and fix tox	2014-07-17 18:13:42 -07:00
tox.ini	Activate pep8 check that _ is imported	2015-08-04 10:52:56 -05:00

README.rst

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:

specs/<release>/

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:

http://blueprints.launchpad.net/cinder

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

https://wiki.openstack.org/wiki/Blueprints

For more information about working with gerrit, see:

http://docs.openstack.org/infra/manual/developers.html#development-workflow

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.