We (the Ironic team) have talked a couple times about keystone /v3 support and about improving the granularity of policy support within Ironic. No one stepped up to work on these specifically, and they weren't prioritized during Liberty ... but I think everyone agreed that we should get on with the keystone v3 relatively soon. If Ironic is the only integrated project that doesn't support v3 yet, then yea, we should get on that as soon as M opens. -Devananda On Fri, Sep 11, 2015 at 9:45 AM, Davanum Srinivas <davanum at gmail.com> wrote: > Hi, > > Short story/question: > Is keystone /v3 support important to the ironic team? For Mitaka i guess? > > Long story: > The previous discussion - guidance from keystone team on magnum > (http://markmail.org/message/jchf2vj752jdzfet) motivated me to dig into the > experimental job we have in devstack for full keystone v3 api and ended up > with this review. > > https://review.openstack.org/#/c/221300/ > > So essentially that rips out v2 keystone pipeline *except* for ironic jobs. > as ironic has some hard-coded dependencies to keystone /v2 api. I've logged > a bug here: > https://bugs.launchpad.net/ironic/+bug/1494776 > > Note that review above depends on Jamie's tempest patch which had some hard > coded /v2 dependency as well (https://review.openstack.org/#/c/214987/) > > follow up question: > Does anyone know of anything else that does not work with /v3? > > Thanks, > Dims > > -- > Davanum Srinivas :: https://twitter.com/dims > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >