Fuel designs and specs
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 3baf0bee63 OpenDev Migration Patch 1 month ago
doc/source Replace deprecated library function os.popen() with subprocess 3 years ago
images Support custom CA bundle file to use in verifying the vCenter server certificate. 2 years ago
policy Deprecate Fuel-wide CL role 3 years ago
specs Update spec for custom workflows UI according to its final implementation 2 years ago
tests Run spec checks for newton (10.0) release 2 years ago
tools Initial commit 5 years ago
.gitignore Team Structure policy document 3 years ago
.gitreview OpenDev Migration Patch 1 month ago
.testr.conf Initial commit 5 years ago
LICENSE Initial commit 5 years ago
README.rst Show team and repo badges on README 2 years ago
requirements.txt Blueprint: snapshot-download-with-auth 4 years ago
setup.cfg Initial commit 5 years ago
setup.py Initial commit 5 years ago
tox.ini Pass environment variables of proxy to tox 3 years ago


Team and repository tags


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:


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:


Please note, Launchpad blueprints are still used for tracking the current status of blueprints. For more information, see:


For more information about working with gerrit, see:


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.