openstack/vitrage-specs
Code Issues Proposed changes
Vitrage Design Specifications
174 Commits 1 Branch 0 Tags 2.5 MiB
Python 100%
master
Go to file
wu.shiming a29e691e6c Changed minversion in tox to 3.18.0 
The patch bumps min version of tox to 3.18.0 in order to
replace tox's whitelist_externals by allowlist_externals option:
https://github.com/tox-dev/tox/blob/master/docs/changelog.rst#v3180-2020-07-23

Change-Id: I24b41e47ba5b7d6094c05c338dbd1e4206d10f5c
2021-09-18 11:52:41 +08:00
doc/source Remove unicode from specs 2021-01-05 06:54:32 +00:00
specs Remove unicode from specs 2021-01-05 06:54:32 +00:00
tests Initial setup of vitrage-spec project 2015-11-06 13:56:56 +02:00
.gitignore Switch to stestr 2018-07-04 13:54:56 +07:00
.gitreview OpenDev Migration Patch 2019-04-19 19:42:05 +00:00
.stestr.conf Switch to stestr 2018-07-04 13:54:56 +07:00
.zuul.yaml import zuul job settings from project-config 2018-08-17 14:05:09 +09:00
bindep.txt [ussuri][goal] Drop python 2.7 support 2019-12-30 12:22:09 +00:00
LICENSE Initial setup of vitrage-spec project 2015-11-06 13:56:56 +02:00
README.rst Update the governance link 2018-08-27 22:30:41 -04:00
requirements.txt Switch to newer openstackdocstheme version 2020-06-02 14:05:12 +02:00
setup.cfg setup.cfg: Replace dashes with underscores 2021-05-04 16:58:45 +08:00
setup.py Initial setup of vitrage-spec project 2015-11-06 13:56:56 +02:00
tox.ini Changed minversion in tox to 3.18.0 2021-09-18 11:52:41 +08:00

README.rst

Team and repository tags

image

OpenStack Vitrage Specifications

This git repository is used to hold approved design specifications for additions to the Vitrage 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>/

Where there are two sub-directories:

specs/<release>/approved: specifications approved but not yet implemented specs/<release>/implemented: implemented specifications

This directory structure allows you to see what we thought about doing, decided to do, and actually got done. Users interested in functionality in a given release should only refer to the implemented directory.

You can find an example spec in doc/source/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.

Launchpad blueprints:

http://blueprints.launchpad.net/vitrage

Starting from the Mitaka-1 development milestone Vitrage performs the pilot of the specs repos approach.

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.

To build the document automatically on changes, use the command:

$ tox -e autobuild

Then open in a browser http://localhost:8000