CloudKitty (Rating) design specification
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
OpenDev Sysadmins 5b214217bc OpenDev Migration Patch 6 days ago
doc/source Initializing the Train specs 3 weeks ago
specs Spec: Add some concurrency and parallelism to the processor 2 weeks ago
.gitignore Initialize cloudkitty-specs repo 2 years ago
.gitreview OpenDev Migration Patch 6 days ago
.zuul.yaml import zuul job settings from project-config 7 months ago
LICENSE Initialize cloudkitty-specs repo 2 years ago
README.rst Refreshing the repository 6 months ago
requirements.txt Remove yasfb dependency 4 weeks ago
setup.cfg Fix author-email in setup.cfg 3 months ago
setup.py Initialize cloudkitty-specs repo 2 years ago
tox.ini fix tox python3 overrides 7 months ago

README.rst

OpenStack Cloudkitty Specifications

This git repository is used to hold approved design specifications for additions to the Cloudkitty 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 story for a given release can be found by looking at the story in Storyboard. Not all stories 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.

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.