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). After the Keystone change lands, I will update the NestedQuota support to handle domain_id being the parent of a top level project, and then update Tempest tests so we get coverage on both Cinder nested and non-nested quotas. - Ryan McNair (mc_nair) > 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. > > Cheers, > Raildo