openstack
/
fuel-specs
Code Issues Proposed changes
RETIRED, Fuel designs and specs
435 Commits 1 Branch 0 Tags 24 MiB
Go to file
Vladimir Kozhukalov f66d1f5a1f Deprecate Fuel-wide CL role 
As far as we are on our way to make Fuel even
more modular this patch deprecates the role CL
as a Fuel-wide role. Instead Fuel should become
and aggregator of features that provide independent
components. It should be up to a component team
to decide whether they need formal or informal CL.
It also should be up to them how they make architectural
and planning decisions.

Change-Id: Idc35b37711e329a41501246cd082d34eef1e2207
 		2016-04-07 12:26:19 +03:00
doc/source Replace deprecated library function os.popen() with subprocess 2016-01-14 04:30:06 -08:00
images Merge "Add spec for graceful cluster stop" 2016-03-04 19:14:57 +00:00
policy Deprecate Fuel-wide CL role 2016-04-07 12:26:19 +03:00
specs Merge "Add spec for deployment info history in DB" 2016-03-24 16:09:53 +00:00
tests Template: OSCI impact moved under Infra impact 2015-10-28 17:50:45 +09: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 Workflow documentation is now in infra-manual 2014-12-05 03:30:44 +00: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

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.