womax/nova
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

nova-manage: Add flavor scanning to migrate_to_unified_limits

Browse Source 
This makes 'nova-manage limits migrate_to_unified_limits' scan the API
database for flavors and detect if any resource classes are missing
registered limits in Keystone.

Related to blueprint unified-limits-nova-unset-limits

Change-Id: I431176fd4d09201c551d8f82c71515cd4616cfea
This commit is contained in:
melanie witt
2024-07-13 08:23:37 +00:00
parent 3b530ac15b
commit 294e21c803
9 changed files with 636 additions and 75 deletions
Download Patch File Download Diff File Expand all files Collapse all files
releasenotes/notes/unified-limits-flavor-scan-3e41db3379ed0aba.yaml
+12
View File
@@ -0,0 +1,12 @@
features:
- |
The ``nova-manage limits migrate_to_unified_limits`` command will now scan
the API and cell databases to detect resource classes that do not have
registered limits set in Keystone and report them to the console.
The purpose of the flavor scan is to assist operators who are migrating
from legacy quotas to unified limits quotas. The current behavior with
unified limits is to fail quota checks if resources requested are missing
registered limits in Keystone. With flavor scanning in
``migrate_to_unified_limits``, operators can easily determine what resource
classes for which they need to create registered limits.