[openstack-dev] Keystone Service Catalog endpoints vs. API versions
Gabriel.Hurley at nebula.com
Fri Apr 26 21:20:38 UTC 2013
I've been working on API version selection in Horizon and came to an odd realization:
Keystone's service catalog can (and in the case of devstack currently does) send out an endpoint for a version which is not the latest stable API. In this case we have the Keystone v3 API, but devstack sets the Keystone SC entry to v2.
This leaves me with three options:
1. Treat the Service Catalog's version choice as the "preferred" API version and just go with it.
2. Treat the Service Catalog as a "suggested" version but query the root of the API to see if there's a different version which Horizon would prefer.
3. Rewrite/redefine the service catalog so that it only returns the hosts/ports for the services. This would require a lot of reworking in the clients, too.
I'm interested in input from the community; option 1 is the easiest, option 2 solves the problem for me, and option 3 is superior insofar as allowing flexible version choosing based on the what the consumer is able to handle but requires the most work.
More information about the OpenStack-dev