reservations.
>
>3. Do we really need it ?
>
Seems like we need *some* way of keeping track of usage
reserved during a particular request and a way to easily
roll that back at a later time. I'm open to alternatives
to reservations, just wondering what the big downside of
the current rese
disable -1 support for now, etc. - all input is welcome.
Thanks,
Ryan McNair (mc_nair)
[1] https://review.openstack.org/#/c/285640/2
[2] https://bugs.launchpad.net/cinder/+bug/1552944
__
OpenStack Development Mailing List
). 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 r
