Jclouds fails with Keystone V3 API Token
I think I was wrong, Token object contains details related to the catalog and endpoints so it is fine
I had a look at the keystone v3, they are quite richer than v2 and lots of new things there
in particular, in v3 token mgmt needs to be a bit different as the response payload doesn't contain the token id (it is stored on a header)
Also the "token" payload doesn't contain the services/endpoints as Access returned by https://developer.openstack.org/api-ref/identity/v2/index.html#authenticate so I think we need to use https://developer.openstack.org/api-ref/identity/v3/index.html#service-catalog-and-endpoints
Anyone has an idea of what privileges I need to invoke /v3/endpoints as I get 403 Forbidden with my account?
jclouds is community-developed software and thus this feature will be implemented when a volunteer contributes it. Would you like to volunteer?
can anyone give an update on this issue. Any tentative date for its resolution ?
Apologies but I won't be able to help out here.
hi Zack Shoylev, Everett Toews,
I think supporting Openstack Keystone v3 is becoming really urgent as v2 is deprecated.
Happy to help here, but do you guys know if there are openstack experts like you guys that can help here as well?
There is no date yet. I have to study the best way to implement it, but my intention is to make it transparent for users and let jclouds pick the right version of keystone based on the apiVersion field that can be configured when creating the context.
Thanks a lot.
Is there a tentative date though? Will it be a big change ?
This is in mi high priority list, but I haven't been able to commit time to this yet. There are a lot of changes going on in Azure ARM that unfortunately go first in the queue, but I expect to start working on this issue as soon as we're done with Azure ARM (we're almost there).
Is there any update on this? Keystone v3 Support is almost mandatory now. Please let me know if there is any progress or if any one can give any pointers we can try it from our end.
As per Keystone community, API v2 will be removed in Q release. At this point Pike is under development. If v3 is not supported then jclouds may be unusable with OpenStack beginning next release.
With OpenStack Mitaka release keystone deprecated all v2.0 APIs. The keystone team recommends using v3 APIs instead.
Please re-consider to support Keystone v3 API. thanks!
I did start, but unfortunately got bogged down in the complexity of the jclouds code and ultimately we ended up using openstack4j instead.
Have you started worked on this issue? I am also very interested in this feature and would be willing to help if I can.
I'd like to start working on this - could someone assign me to the ticket so I can mark it as "In progress"?
Please update on the progress of this task.Is there timeline published for the 1.7 release ?