Uops, sorry :)
https://blueprints.launchpad.net/keystone/+spec/service-catalog-version-support
I don't know if this was actually implemented in any of the old
OpenStack versions and if they are returning it now. I hope other
OpenStack folks in this link can clarify this. I saw the usage of the
Thanks Ignassi for confirming my suspicions.
I think you forgot to include the blueprint [1] reference you mentioned
below...
--Ryan
On Jan9 9:00 AM, Ignasi Barrera wrote:
Hi Ryan,
Apologies for the late reply. The problem here is that no v2.0
identity endpoint is returned in the service
Hi Ryan,
Apologies for the late reply. The problem here is that no v2.0
identity endpoint is returned in the service catalog. As you say,
jclouds does the version discovery and it can only work with the
endpoints returned in the service catalog. An initial request is
performed to authenticate the
Hi,
I'm hoping to get a better understanding of how jclouds discovers and
decides which identity endpoint to use. Feel free to redirect me to
docs if this is already written up somewhere.
In my case, we have a community Mitaka installation running and an app
that uses jclouds v2.0.0.
