Go to file
Kiran Pawar 9c49b28d61 Add spec for qos types
New object qos_type along-with its specs will be used to define
Quality of Service that driver can implement on Manila resource e.g.
share. The driver must report capability `qos_type_support` and
share-type extra-spec named `default_qos_type` must have valid
qos_type name as its value.

Implement: blueprint qos-types
Change-Id: If35b4a3b020b5a0f0d81aec3567a02500b839bb1
Signed-off-by: Kiran Pawar <kinpaa@gmail.com>
2025-12-11 08:48:26 +00:00
2025-12-11 08:48:26 +00:00
2025-12-11 08:48:26 +00:00
2021-05-25 19:45:05 +05:30
2019-04-19 19:33:23 +00:00
2016-05-12 14:51:16 +00:00
2018-08-19 04:25:57 +08:00
2016-05-12 14:51:16 +00:00
2017-11-17 13:41:24 -05:00
2021-05-25 19:45:05 +05:30

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.

Description
Specs repo for Manila (OpenStack Shared File Systems) project.
Readme 5.1 MiB
Languages
Python 100%