openstack
/
manila-specs
Code Issues Proposed changes
Specs repo for Manila (OpenStack Shared File Systems) project.
166 Commits 1 Branch 0 Tags 4.6 MiB
Python 100%
Go to file
haixin 899ea32680 Share size limited by share type 
Add support for limit the size of share through the share type, the
share created by the user shall not be greater than the maximum value
set in the share type and shall not be less than the minimum value set.
Of course, depending on the usage scenario, only a maximum or a minimum
can be set.

Partially-Implements: blueprint share-size-limited-by-share-type
Change-Id: Ie03a4564ddcacd9b084db09b76be55d15080133f
 		2020-12-02 09:08:26 +08:00
doc/source Add Wallaby release 2020-10-13 15:06:06 -03:00
specs Share size limited by share type 2020-12-02 09:08:26 +08:00
.gitignore Add line for PyCharm IDE in gitignore file 2018-06-27 17:58:35 -04:00
.gitreview OpenDev Migration Patch 2019-04-19 19:33:23 +00:00
.testr.conf Create skeleton using cookiecutter 2016-05-12 14:51:16 +00:00
.zuul.yaml import zuul job settings from project-config 2018-08-20 18:49:43 +00:00
CONTRIBUTING.rst Create skeleton using cookiecutter 2016-05-12 14:51:16 +00:00
LICENSE Create skeleton using cookiecutter 2016-05-12 14:51:16 +00:00
README.rst Update links in README 2018-08-19 04:25:57 +08:00
requirements.txt Switch to newer openstackdocstheme version 2020-05-31 17:56:34 +02:00
setup.cfg Cleanup py27 support 2020-06-04 18:00:59 +02:00
setup.py Create skeleton using cookiecutter 2016-05-12 14:51:16 +00:00
test-requirements.txt Remove unit test targets 2017-11-17 13:41:24 -05:00
tox.ini Cleanup py27 support 2020-06-04 18:00:59 +02:00

README.rst

Team and repository tags

image

OpenStack Manila Specifications

This git repository is used to hold approved design specifications for additions to the Manila 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 Newton development cycle, this repository was not used for spec reviews. Reviews prior to Newton were completed entirely informally using wiki pages linked from blueprints:

https://blueprints.launchpad.net/manila

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:

https://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.