[openstack-dev] Consistent Versioned Endpoints

Scott D'Angelo scott.dangelo at gmail.com
Thu Jan 12 18:35:21 UTC 2017

TL;DR: Let's discuss Version Discovery and Endpoints in the Service Catalog
at the PTG in Atlanta.

The topic of Versioning and the Endpoints discovered in the Service Catalog
was discussed in today's API Working Group Meeting[1].
A previous ML post[2] claimed:

In a perfect world, every endpoint would return the same type of resource -
most likely the versions resource as described in the API WG Microversions
spec. It would also be nice if version negotiation can happen without
requiring authentication, the easiest path to which would be supporting the
'max_version' and 'min_version' fields in the root versions resource.

One problem is multiple versioned service names in the catalog for a given
service[3], as opposed to a single endpoint that would return version

Can we get to this "perfect world"? Let's discuss at the PTG.....
It is my understanding that we do not have the ability to schedule a time
or room for such a cross-project discussion. Please chime in if interested,
and/or make your interest known to scottda, mordred, or edleafe.

Scott D'Angelo
scott.dangelo at ibm.com

[3] http://paste.openstack.org/show/594751/
[4] http://paste.openstack.org/show/594754/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170112/bcfb3776/attachment.html>

More information about the OpenStack-dev mailing list