RETIRED, Fuel designs and specs
Go to file
Julia Aranovich 9f94b695b2 Spec for node list sorters and filters
Blueprint node-list-sorters-and-filters

Change-Id: Ibd78db91186515ddf1f2a2883dd9e7b8c8032323
2015-06-26 16:26:04 +03:00
doc/source Dynamic index.rst for specs 2015-06-18 13:37:09 +00:00
images Spec for node list sorters and filters 2015-06-26 16:26:04 +03:00
specs Spec for node list sorters and filters 2015-06-26 16:26:04 +03:00
tests Specification for sending statistics 2014-11-10 13:26:45 +03:00
tools Initial commit 2014-05-26 18:58:40 +04:00
.gitignore Compress upgrade tarball with lrzip 2014-09-02 21:39:40 +04:00
.gitreview Added .gitreview 2014-05-22 00:53:07 +00:00
.testr.conf Initial commit 2014-05-26 18:58:40 +04:00
LICENSE Initial commit 2014-05-26 18:58:40 +04:00
README.rst Workflow documentation is now in infra-manual 2014-12-05 03:30:44 +00:00
requirements.txt Loss of .gitignore file 2014-06-30 19:46:33 +08:00
setup.cfg Initial commit 2014-05-26 18:58:40 +04:00
setup.py Initial commit 2014-05-26 18:58:40 +04:00
tox.ini Copied and updated image based provisioning spec 2014-10-20 16:09:37 +04:00

Fuel Specifications

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

Prior to the Juno development cycle, this repository was not used for spec reviews. Reviews prior to Juno were completed entirely through Launchpad blueprints:

http://blueprints.launchpad.net/fuel

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.