Excellent start @nacx! I think [1] and [2] may help our discussion.
Andrea [1]: https://specs.openstack.org/openstack/keystone-specs/api/v3/identity-api-v3-v2-comparison.html [2]: http://docs.openstack.org/developer/keystone/http-api.html Andrea Il 02/apr/2016 19:08, "Ignasi Barrera" <ignasi.barr...@gmail.com> ha scritto: > Hi! > > There were no plans (yet) to add support for v3, mainly because apart > from the JIRA issue there have not been discussions here or community > requests for that. Now that there is real interest from the community > it's time to see how we can make it happen :) > > The easiest way to get things done is to get involved and... just > start doing them. I'm pretty sure Andrea suggested that because the > first issue here might be the available cycles of some of the main > contributors, so any help to get started would be highly appreciated. > > Some of us are not yet familiar with the differences in the v3 API and > what changes would be required, so I'd suggest we start planning: > > 1. How we will deliver the new version of Keystone while keeping the old > one. > 2. What changes in the new version of the API. Does it require an > entire rewrite? Are there significant changes to the service catalog? > (we use it in every OpenStack API we have, so that's the real critical > path). > > Those two points should generate the tasks needed to start adding > support. Once those are done or someone starts them, it will be easier > to continue completing the new API features. > > > Thanks for starting this thread! > > I. > > (P.S. I've explicitly added Zack to the thread) > > On 2 April 2016 at 01:36, Morgan Fainberg <morgan.fainb...@gmail.com> > wrote: > > The idea here was to ensure we started the conversations long before the > Q > > release (we're about 1.5 years out) came along and jclouds no longer > > worked. A long lead time here is essential to the thriving ecosystem > around > > OpenStack. > > > > Steve and I can (initially) help connect with folks in OpenStack and/or > > answer questions around behaviors of keystone and auth as needed (forward > > looking and otherwise) and/or connect you with the wider community. > > > > Cheers, > > --Morgan > > > > On Fri, Apr 1, 2016 at 4:33 PM, Apoorva Deshpande <apoor...@tintri.com> > > wrote: > > > >> Unfortunately I don’t have time to participate in the effort. > >> Since Keystone v3 support is critical to our clients we would need to > >> explore alternatives to jclouds. > >> > >> > >> > >> > >> On 4/1/16, 9:14 AM, "Andrea Turli" <andrea.tu...@gmail.com> wrote: > >> > >> >Hi Apoorva, > >> > > >> >Not planned yet, afaik, are you keen to help with that? > >> > > >> >Andrea > >> > > >> >Il ven 1 apr 2016 14:32 Apoorva Deshpande <apoor...@tintri.com> ha > >> scritto: > >> > > >> >> (cc: Keystone core team members ) > >> >> > >> >> Hello All, > >> >> > >> >> We use jclouds to communicate with OpenStack Keystone. I wanted to > know > >> if > >> >> jclouds is planning to support Keystone API version 3? > >> >> As I understand, Keystone v2 is (mostly) deprecated and will be > removed > >> >> from OpenStack Q release. > >> >> > >> >> I found following bug which tracks Keystone v3 support ( which is in > >> >> open-unresolved state. ) > >> >> > >> >> https://issues.apache.org/jira/browse/JCLOUDS-114 > >> >> > >> >> > >> >> Also following few email archives [1][2] talk about the same issue. > >> >> > >> >> > >> >> Please let me know if this work is on the roadmap. > >> >> > >> >> > >> >> Thanks, > >> >> > >> >> Apoorva > >> >> > >> >> > >> >> [1] > http://www.mail-archive.com/user%40jclouds.apache.org/msg01807.html > >> >> > >> >> [2] > http://www.mail-archive.com/dev%40jclouds.apache.org/msg06048.html > >> >> > >> >
