Open Stack

-1

Unless there's something more to this, I don't think it's worth any sort of
risk to stability just to shuffle API implementations around that can't
wait for mikata.

On Fri, Sep 4, 2015 at 12:28 PM, Henry Nash <henryn at linux.vnet.ibm.com>
wrote:

> Keystone has, for a number of releases,  supported the concept of
> inherited role assignments via the OS-INHERIT extension. At the Keystone
> mid-cycle we agreed moving this to core this was a good target for Liberty,
> but this was held by needing the data driver testing to be in place  (
> https://review.openstack.org/#/c/190996/).
>
> Inherited roles are becoming an integral part of Keystone, especially with
> the move to hierarchal projects (which is core already) - and so moving
> inheritance to core makes a lot of sense.  At the same time as the move, we
> want to tidy up the API (https://review.openstack.org/#/c/200434/
> <https://review.openstack.org/#/c/187045/>) to be more consistent with
> project hierarchies (before the old API semantics get too widely used),
> although we will continue to support the old API via the extension for a
> number of cycles.
>
> I would like to request an FFE for the move of inheritance to core.
>
> Henry
>
> __________________________________________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150904/06cd892d/attachment.html>