-
Epic
-
Resolution: Done-Errata
-
Normal
-
rhos-18.0.0
-
Unified Limits Integration in Nova
-
False
-
False
-
OSPRH-811Red Hat OpenStack 18.0 Greenfield Deployment
-
Committed
-
No Docs Impact
-
OSPRH-811 - Red Hat OpenStack 18.0 Greenfield Deployment
-
openstack-nova-27.1.1-18.0.20230930093334.a869ab1.el9ost
-
Committed
-
No impact
-
0% To Do, 0% In Progress, 100% Done
-
-
Technology Preview
-
Done
-
Rejected
Description of problem:
Support for keystone unified limits in nova
for centralized quota and resource limits.
The work on unified limtis has been ongoing for several cycles.
https://review.opendev.org/#/c/602201/
to move that effort forword requires a multi cycle investment
While much work has been done to simplify how quotas are implemented in
Nova, there are still some major usability issues for operators with
the current system:
- We don't have consistent support for limit/quota hierarchy across OpenStack
- Requiring operators to set limits individually in each service
(i.e. Cinder, Nova, Neutron, etc) - Nova's existing quotas don't work well with Ironic
- No support for custom Resource Class quotas (includes "per flavor" quotas)
- Confusion when API defined quota limits override any changes made to the
configuration - Some Nova quotas are unrelated to resource consumption, causing confusion
Transitioning to use Keystone's unified limits, via oslo.limit, will help fix
these issues.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
- is cloned by
-
OSPRH-8622 Unified Limits Integration in Nova
- Backlog
- is related to
-
OSPRH-197 Backport tooling to migrate quota limits from nova to keystone
- Backlog
- external trackers
- links to
-
RHBA-2023:116856 Release of components for OSP 18.0
-
RHBA-2024:133297 Release of components for Red Hat OpenStack Services on OpenShift 18.0