Config option to control behavior of unset unified limits
The default behavior in the oslo.limit quota enforcement library used by Nova
when ``[quota]driver`` is set to ``nova.
consider resources that do not have registered limits set as having a limit of
zero. This behavior can be unforgiving especially in the scenario of an
upgrade that enables unified limits quota (i.e. if we ever want to make unified
limits the default). If we make the behavior configurable within Nova, we can
help prevent situations where an admin/operator upgrades or installs Nova and
suddenly all API requests begin to be rejected for being over quota.
Blueprint information
- Status:
- Complete
- Approver:
- Sylvain Bauza
- Priority:
- Undefined
- Drafter:
- melanie witt
- Direction:
- Approved
- Assignee:
- melanie witt
- Definition:
- Approved
- Series goal:
- Accepted for 2025.1
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Sylvain Bauza
- Completed by
- Sylvain Bauza
Related branches
Related bugs
Sprints
Whiteboard
Addressed by: https:/
Add config option [quota]
Gerrit topic: https:/
Addressed by: https:/
nova-manage: Add flavor scanning to migrate_
[20240717 bauzas] Spec approved for the Dalmatian release
Gerrit topic: https:/
Addressed by: https:/
Re-propose config option for behavior of unset unified limits
[20250106 bauzas] Spec was reapproved for Epoxy
Gerrit topic: https:/
Addressed by: https:/
Bump requirement to PrettyTable>=2.4.0
