openstack
/
manila-specs
Code Issues Proposed changes
Specs repo for Manila (OpenStack Shared File Systems) project.
110 Commits 1 Branch 0 Tags 4.6 MiB
Python 100%
Go to file
Goutham Pacha Ravi 7689f3a8cb import zuul job settings from project-config 
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.

Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.

Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.

See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html

Change-Id: Ic6a518219cf09a43637ac719afcfdda4d1ece360
Story: #2002586
Task: #24309
 		2018-08-20 18:49:43 +00:00
doc/source Remove out of date priorities section 2018-05-22 18:22:16 -04:00
specs Merge "Trivial: Update pypi url to new url" 2018-05-02 08:04:53 +00:00
.gitignore Add line for PyCharm IDE in gitignore file 2018-06-27 17:58:35 -04:00
.gitreview Added .gitreview 2016-05-04 06:26:17 +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 Optimize the link address 2017-04-11 11:56:58 +05:30
requirements.txt Switch to openstackdocstheme 2018-04-27 13:27:29 -07:00
setup.cfg Remove pbr warnerrors in favor of sphinx check 2017-05-23 07:20:15 +00: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 fix tox python3 overrides 2018-07-03 14:45:29 +07: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:

http://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:

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.