openstack
/
murano-specs
Code Issues Proposed changes
RETIRED, Murano Design Specifications
145 Commits 1 Branch 0 Tags 2.7 MiB
Go to file
OpenDev Sysadmins 09424cf499 OpenDev Migration Patch 
This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
 		2019-04-19 19:33:56 +00:00
doc/source Update spec repo config 2017-06-02 13:11:28 +03:00
specs Fix the misspelling of "configuration" 2018-12-26 22:01:45 +08:00
tests Initial setup of spec project 2014-11-18 22:34:38 +03:00
.gitignore Initial setup of spec project 2014-11-18 22:34:38 +03:00
.gitreview OpenDev Migration Patch 2019-04-19 19:33:56 +00:00
.testr.conf Initial setup of spec project 2014-11-18 22:34:38 +03:00
.zuul.yaml import zuul job settings from project-config 2018-08-23 12:01:21 +00:00
LICENSE Initial setup of spec project 2014-11-18 22:34:38 +03:00
README.rst Show team and repo badges on README 2016-11-25 15:53:52 +01:00
requirements.txt Update spec repo config 2017-06-02 13:11:28 +03:00
setup.cfg Change openstack-dev to openstack-discuss 2018-12-04 18:37:17 +00:00
setup.py Update spec repo config 2017-06-02 13:11:28 +03:00
tox.ini fix tox python3 overrides 2018-10-08 07:50:50 +00:00

README.rst

Team and repository tags

image

OpenStack Murano Specifications

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

Where there are two sub-directories:

specs/<release>/approved: specifications approved but not yet implemented specs/<release>/implemented: implemented specifications

This directory structure allows you to see what we thought about doing, decided to do, and actually got done. Users interested in functionality in a given release should only refer to the implemented directory.

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 Kilo development cycle this repository was not used for spec reviews. Reviews prior to Juno were completed entirely through Launchpad blueprints:

http://blueprints.launchpad.net/murano

Starting from the Kilo-1 developement milestone Murano performs the pilot of the specs repos approach.

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.