This repo is now testing only with Python 3, so let's make
a few cleanups:
- Remove python 2.7 stanza from setup.py
- Remove obsolete sections from setup.cfg
- Remove install_command from tox.ini, the default is fine
Change-Id: I6639d4b8612f9f50c98da43aec24cc7dbdb87634
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: Iaaaaa34ba7c0bfb573feb40404be6eeec5aeeaae
Story: #2002586
Task: #24757
Going back to essex this is fairly easy since we had
API samples for the / versions document in the integrated
tests.
After that it gets a bit weird.
We have diablo-eol in github and the versions can be pulled
from code and unit tests there.
We don't have -eol tags for austin, bexar or cactus, so
we have to check tags.
The last release for cactus was 2011.2 and we can pull
the versions from code and tests.
The last release for bexar was 2011.3.1 and we can pull
the versions from code and tests.
We don't have any release tag for austin in the git repo
even though the openstack releases page says 2010.1 was
the austin release. We can find the 2010.1 nova code on
launchpad:
https://launchpad.net/nova/austin/2010.1
And looking in nova/api/__init__.py we see the
osapi_versions method on the API router class, which shows
the same version (v1.0) as in Bexar.
Per the validation in this repo, all 'links' and 'updated'
keys in responses are removed even if they are in the
actual responses.
This change also updates the schema, and fixes part of it:
1. The README says status can include "EXPERIMENTAL" but that
wasn't defined as an option in the schema.
2. The "required" key was misspelled.
3. Nova uses "version" instead of "max_version" for microversions,
so that is added to the schema and README.
4. And for crying in the soup Martha, format the json schema!
Change-Id: I4f353451f2cd2e06c1bb34d695f926e88108c219
Adds the version history files for Glance from Bexar through Mitaka,
plus the version history file for Ocata.
Change-Id: I1626ada8ba00912f9cad01d7708c6750b6152772
Define the structure of the documents and also provide a way to validate
incoming patches against it. (The setup.py and setup.cfg are there just
to empower tox to run the test script)
Change-Id: I819c2df1c7c9081bd6f51caae1e4f3794275abaa
Since each of the services already have a version discovery document which
is very suitable, except for containing some formatting differences and some
additional data, define a format that is mechanically derivable from the
existing documents.
It should be noted that a mapping must exist _somewhere_ between project
names and service types. This does not attempt to solve that, but the
process described within assumes the existence of the
service-types-registry.
It should be also noted that this list is not complete - it is merely
the list of available services I could check by hand on Vexxhost, which
I happen to know is running Newton. Hopefully it is both enough of a
straw-man document and a complete enough process for how projects might
maintain such a document going forward that we can finish it as a group
exercise.
Change-Id: If50f6b0ef39cd37ac8640bc653e89d98eb4963b3