The api documentation is now published on docs.openstack.org instead
of developer.openstack.org. Update all links that are changed to the
new location.
Note that redirects will be set up as well but let's point now to the
new location.
For details, see:
http://lists.openstack.org/pipermail/openstack-discuss/2019-July/007828.html
Change-Id: Id60f5c97058646c19a8a9d0befc56e9e97b202d8
The patches from the proposal bot are large and unreadable because our
starting data is not sorted like the data that we're publishing now is.
Sort the current data by hand so that the proposal bot changes can
actually be read.
Change-Id: I6066d7f74b7abee87a63115941bdced1d44e39b7
The sync job isn't working, so let's do one by hand. This includes the
senlin change to clustering.
Before we sync again, let's also get ost to use OrderedDict so that the
json emitted is consistent from change to change and we can validate
these easier.
Change-Id: Iee84f555a65170ac9969486c89a25bfb33595c52
The service type authority is publishing three new pre-computed
mappings. Add getters to expose them and use them where appropriate.
Also, add a method that will return all of the service data for a
project with more than one service to complement the one that only
returns the primary data.
Depends-On: Ib761cf9de875e7b80404797d4aa8d294ca56347a
Change-Id: I78d2dfa03a5a0c392a85a7a77612098b4b01f70e
The data now allows marking a service as secondary to support
placement/compute in nova. Support that in by_project.
Adds placement to the built-in data so that we can see the testing of
it. We should not approve this patch until approving the Add placement
service patch.
Change-Id: I01ad2934bdcb9346f4af88520f572d9b4f852b5d
There have been two changes to service-types-authority data which break
the unittests for os-service-types. Some of the url schemes were set to
https instead of http, and the order of the volume aliases changed.
Update the unittests so that we can sync data updates again. Sync one by
hand to verify the updates.
Change-Id: Ic323db63b1ab8e74284bdd32a858cb1722a0d4ed
Depends-On: I3086dcfb85f5ca9970f018d503c9378f307a3e73
Refresh the local copy of service-types.json with the latest version
from service-types-authority.
Change-Id: If9780d7896c05f02e29bc5bd14ad6beec3a1c267
The ServiceTypes class is the main entry point for python programmers.
It should allow them to answer the questions they have about the data
without necessarily walking the structure. It can also return the raw
structure if people want to get at it.
We need to know the project codename for services for doing API doc
publication validation and also for being able to send legacy
microversion headers. The information is in the data, use it.
In order to construct and send microversion headers for projects with
aliases, we need to know ALL of the aliases plus the official name,
because we don't know which one of the values will be the correct name
the service is looking for for a given version. The microversion spec,
however, requires that consumers be able to handle a header that
contains a list of services and to ignore the ones it isn't looking for.
By providing a a list of all the possible values we make it easy to
construct a header for a service given a service_type that should work
for all known identifiers of the service and that is future compatible
with the service-type and microversion specifyier aligning.
Co-Authored-By: Doug Hellmann <doug@doughellmann.com>
Change-Id: I57641c9e3c27688b6d7709b1bb07292740d26659