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 info[4]. 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.dang...@ibm.com [1] http://eavesdrop.openstack.org/meetings/api_wg/2017/api_wg.2017-01-12-16.00.log.html [2] http://lists.openstack.org/pipermail/openstack-dev/2016-August/102549.html [3] http://paste.openstack.org/show/594751/ [4] http://paste.openstack.org/show/594754/
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
