RETIRED, Fuel designs and specs
Go to file
blue55 ee7eab67cf Fix html_last_updated_fmt for Python3
Fix the Sphinx html_last_updated_fmt for Python3. The
html_last_updated_fmt option is interpreted as a byte
string in python3, causing Sphinx build to break.
This patch makes it utf-8 string.

Change-Id: I8d47b0ab690fd682c4e72b742b68b7bf9201557a
2017-06-19 12:15:33 +08:00
doc/source Fix html_last_updated_fmt for Python3 2017-06-19 12:15:33 +08:00
images Support custom CA bundle file to use in verifying the vCenter server certificate. 2016-08-25 16:43:02 +03:00
policy Deprecate Fuel-wide CL role 2016-04-07 12:26:19 +03:00
specs Update spec for custom workflows UI according to its final implementation 2017-02-10 13:26:32 +04:00
tests Run spec checks for newton (10.0) release 2016-08-05 18:42:22 +03:00
tools Initial commit 2014-05-26 18:58:40 +04:00
.gitignore Team Structure policy document 2015-09-24 10:35:04 -07:00
.gitreview Update path due to stackforge migration 2015-10-19 14:01:26 +03: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 Show team and repo badges on README 2016-11-25 17:37:44 +01:00
requirements.txt Blueprint: snapshot-download-with-auth 2015-06-23 11:07:42 +02: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 Pass environment variables of proxy to tox 2015-12-11 08:20:04 +00:00

README.rst

Team and repository tags

image

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.