openstack
/
openstack-ansible-specs
Code Issues Proposed changes
Design Specifications for OpenStack-Ansible
204 Commits 1 Branch 0 Tags 2.4 MiB
Python 100%
Go to file
Ghanshyam Mann 3e6eab5fc3 [ussuri][goal] Updates for python 2.7 drop 
OpenStack is dropping the py2.7 support in ussuri cycle.

openstack-ansible repos need few updates on requirements
and tox file.

Complete discussion & schedule can be found in
- http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010142.html
- https://etherpad.openstack.org/p/drop-python2-support

Ussuri Communtiy-wide goal:
https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html

Change-Id: Ic6cb1eb547efa7cda472950a49dd8adbd7760ffe
 		2020-02-29 18:42:40 -06:00
doc/source Update Specs to use openstackdocstheme 2019-10-01 18:20:49 +03:00
specs fix misspelling 2019-10-01 15:31:45 +00:00
tests Cleaned up specs directory 2015-07-24 08:33:20 -05:00
tools Initial commit for OS-Ansible-Deployment specs 2015-03-17 14:19:19 -05:00
.gitignore Updated from OpenStack Ansible Tests 2018-10-02 14:56:35 +00:00
.gitreview OpenDev Migration Patch 2019-04-19 19:36:19 +00:00
.testr.conf Initial commit for OS-Ansible-Deployment specs 2015-03-17 14:19:19 -05:00
.zuul.yaml import zuul job settings from project-config 2018-08-21 13:21:27 +00:00
LICENSE Initial commit for OS-Ansible-Deployment specs 2015-03-17 14:19:19 -05:00
README.rst Update links in README 2018-03-03 12:19:04 +08:00
requirements.txt [ussuri][goal] Updates for python 2.7 drop 2020-02-29 18:42:40 -06:00
setup.cfg Update mailinglist from dev to discuss 2018-12-05 09:15:49 +08:00
setup.py Updated from global requirements 2017-03-02 11:52:34 +00:00
tox.ini [ussuri][goal] Updates for python 2.7 drop 2020-02-29 18:42:40 -06:00

README.rst

Team and repository tags

image

OS-Ansible-Deployment Specifications

This git repository is used to hold approved design specifications for additions to the OS-Ansible-Deployment 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 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:

https://blueprints.launchpad.net/openstack-ansible

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.