[oslo][keystone] admin-ness not properly scoped and oslo.policy current status about this issue
openstack at nemebean.com
Wed Mar 13 17:30:53 UTC 2019
Tagging Keystone as I think they are better suited to answering this.
A bit more from my limited knowledge inline.
On 3/13/19 12:07 PM, Herve Beraud wrote:
> ## Overview
> I want to bring up this topic (admin-ness not properly scoped) to get
> a big picture of the state of this issue and that was needed on the
> oslo.policy side.
> Few weeks ago some RHOSP customers request for an enhancement of
> oslo.policy since their admin domain can manage other domains. They use
For those not rocking fedoras, OSP 13 corresponds to Queens. :-)
> The goal of this ML thread is to help us to track informations about
> this topic and I also planned to discuss about this topic during the
> next oslo meeting (Monday 18 of March).
> ## Details
> After some investigations I've found a lot of related issues on
> launchpad, and a lot of disucssions inside the openstack
> community about this topic.
> First I guess it's not an RFE but it's a known issue.
> This bug has side-effects across several services, not just oslo or
> keystone, making the fix complex to orchestrate across services.
> In a first time, I want to know more about the latest events on this
> topic on the oslo side:
> - the states of the related specs
> - if we need to add more changes to completely fix this issue and/or if
> everything is complete on the oslo side and know since which version. I
> guess this one is related to.
To my knowledge the Oslo side is done. I think we actually added the
necessary fields to oslo.policy (and oslo.context?) at the end of last
cycle. I'm not sure where the Keystone side stands, but I'm sure someone
from that team can provide an update.
Unfortunately, even if Keystone is completely finished, to consume this
I _think_ it's going to require policy changes in all of the consuming
services, and I don't know that any of those have happened yet. I
believe it's a PTG topic for Keystone.
> Also due to the complexity of this issue I guess is not totally fixed on
> the whole openstack components on stein and it can't be fully (whole)
> backported to stable branches, but your point of view is really
> appreciate. In other words I guess some parts are already fixed on some
> components but some services still need to be fixed and the issue
> partially occur on stein, so fix that on stable branches is not really
> possible, can you confirm?
Yeah, I don't expect most of this would be backportable, especially all
the way to Queens.
> Also I've found few related specs that I guess can be useful to track
> the evolution:
> If I missed something useful do not hesitate to reply on and to share it
> with us.
>  https://bugs.launchpad.net/keystone/+bug/968696
>  https://bugs.launchpad.net/keystone/+bug/1783659
>  https://bugs.launchpad.net/nova/+bug/1649532
>  https://bugs.launchpad.net/oslo.policy/+bug/1577996
> Hervé Beraud
> Senior Software Engineer
> Red Hat - Openstack Oslo
> irc: hberaud
> -----BEGIN PGP SIGNATURE-----
> -----END PGP SIGNATURE-----
More information about the openstack-discuss