Shell cannot distinguish V3 API

[Jamie Lennox]

Original question: http://openstack.redhat.com/forum/discussion/comment/1437

When the token returns a v3 URL for the identity API endpoint there is no way for shell to know this. Thus the shell goes ahead and tries to talk the v2 protocol against the v3 API.

Shell doesn't support the V3 api, and i understand there is no intention to (in favour of openstack-client) however how is a client expected to determine the endpoint version from the service catalog? Should we instead be instructing people to point the identity endpoint to the root path and have the client do version discovery from there?

[Dolph Mathews (dolph)]

> there is no way for shell to know this

With version discovery, the provided URL should be queried by the client, which will return a specific version response rather than a multiple choice response. If the client instantiated by the shell requires v2.x and the response is not v2.x, then it seems reasonable for the shell client to abort. Alternatively (I don't think our version response supports this today, but...) a link from a versioned endpoint back to the multiple choice response would allow a client to reliably switch versions if a desirable version was available.

> Should we instead be instructing people to point the identity endpoint to the root path and have the client do version discovery from there?

Yes! :D

[Rami Lehti (ramilehti)]

Just to provide more incentive for fixing this bug: When I follow the installation guide while installing keystone, I cannot verify that the user accounts are configured correctly since the keystone user-list command gives a 404 error.
This is why I think that this bug is incorrectly labelled Wishlist. It is critical for an installation that this works.

[Henrique Truta (henriquetruta)]

It this bug still valid?

[Steve Martinelli (stevemar)]

please use openstackclient as the main CLI for identity operations in openstack