Juju Charms for OpenStack - Specifications
Go to file
James Page 34421843a2 Open for Ussuri release
Carry forward any backlog specs to Ussuri.

Carry forward any approved but still inflight specs to Ussuri.

Move implemented specs for Train to implemented folder.

Misc tidy of line lengths and missing titles in a couple of specs.

Run unit tests in gate under Python 3.

Change-Id: I23a8823568f1ac594982a37095f3e1c532b5ab53
2019-12-20 11:04:18 +00:00
doc/source Open for Ussuri release 2019-12-20 11:04:18 +00:00
specs Open for Ussuri release 2019-12-20 11:04:18 +00:00
tests Review specs for newton, open for ocata 2016-10-17 09:56:21 +01:00
.gitignore Switch to use stestr for unit test 2018-07-17 13:36:45 +07:00
.gitreview OpenDev Migration Patch 2019-04-19 19:33:56 +00:00
.stestr.conf Switch to use stestr for unit test 2018-07-17 13:36:45 +07:00
.zuul.yaml Open for Ussuri release 2019-12-20 11:04:18 +00:00
LICENSE Base 2016-05-26 11:24:00 +01:00
README.rst Update links in README 2018-06-12 14:54:45 +08:00
requirements.txt Fix lint 2019-04-24 08:38:09 +02:00
setup.cfg Replacing the HTTP protocal with HTTPS 2019-02-28 11:11:42 +00:00
setup.py Base 2016-05-26 11:24:00 +01:00
test-requirements.txt Base 2016-05-26 11:24:00 +01:00
tox.ini Avoid pollution and false positives with tox.ini 2019-08-29 09:52:21 -04:00

Team and repository tags

image

README

OpenStack Charm Specifications

This git repository is used to hold approved design specifications for additions to the Charm project. Reviews of the specs are done in gerrit, using a similar workflow to how we review and merge changes to the code itself. For specific policies around specification review, refer to the end of this document.

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

Example specifications

You can find an example spec in specs/template.rst.