Murano Design Specifications
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.
Ghanshyam Mann 878ff2190d [ussuri][goal] Drop python 2.7 support 1 month ago
doc/source Fix murano-specs gate 9 months ago
specs Replace URLs with URLs 8 months ago
tests Initial setup of spec project 5 years ago
.gitignore Initial setup of spec project 5 years ago
.gitreview OpenDev Migration Patch 9 months ago
.testr.conf Initial setup of spec project 5 years ago
.zuul.yaml import zuul job settings from project-config 1 year ago
LICENSE Initial setup of spec project 5 years ago
README.rst Show team and repo badges on README 3 years ago
requirements.txt Fix murano-specs gate 9 months ago
setup.cfg Change openstack-dev to openstack-discuss 1 year ago Update spec repo config 2 years ago
tox.ini [ussuri][goal] Drop python 2.7 support 1 month ago


Team and repository tags


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:


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:

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:

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.