Re: [openstack-dev] [keystone][cinder] Projects acting as a domain at the top of the project hierarchy

So just recapping, http://review.openstack.org/#/c/274825 separates Cinder NestedQuota support into its own driver which is no longer the default. Once ^ lands, http://review.openstack.org/#/c/231289 should no longer be blocked in Tempest (because NestedQuotas support won't get flexed by default).

Re: [openstack-dev] [keystone][cinder] Projects acting as a domain at the top of the project hierarchy

Hi all, I discussed the change with other cores in -keystone and, looking at the API change guidelines, it should be an allowed API change. I had a doubt whether the rule "Changing or removing a property in a resource representation." could make it a forbidden API change or not. However, since it

Re: [openstack-dev] [keystone][cinder] Projects acting as a domain at the top of the project hierarchy

Henry, I know about two patches related: Fixes cinder quota mgmt for keystone v3 - https://review.openstack.org/#/c/253759 Split out NestedQuotas into a separate driver - https://review.openstack.org/#/c/274825 The first one was abandoned, so I think the second patch is enough to fix this issue.

Re: [openstack-dev] [keystone][cinder] Projects acting as a domain at the top of the project hierarchy

Michal & Raildo, So the keystone patch (https://review.openstack.org/#/c/270057/ ) is now merged. Do you perhaps have a cinder patch that I could review so we can make sure that this is likely to work with the new projects acting as domains? Currently