Quota calculation connects to all available cells
Bug #1771810 reported by
Belmiro Moreira
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Surya Seetharaman | ||
Rocky |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Quota utilisation calculation connects to all cells DBs to get all consumed resources for a project.
When having several cells this can be inefficient and can fail if one of the cell DBs is not available.
To calculate the quota utilization of a project should be enough to use only the cells where the project has/had instances. This information is available in nova_api DB.
Changed in nova: | |
assignee: | nobody → Surya Seetharaman (tssurya) |
Changed in nova: | |
status: | Confirmed → In Progress |
Changed in nova: | |
importance: | Low → Medium |
Changed in nova: | |
assignee: | Surya Seetharaman (tssurya) → Matt Riedemann (mriedem) |
Changed in nova: | |
assignee: | Matt Riedemann (mriedem) → Surya Seetharaman (tssurya) |
Changed in nova: | |
assignee: | Surya Seetharaman (tssurya) → Matt Riedemann (mriedem) |
Changed in nova: | |
assignee: | Matt Riedemann (mriedem) → Surya Seetharaman (tssurya) |
To post a comment you must log in.
This seems like either something that should be a part of https:/ /blueprints. launchpad. net/nova/ +spec/handling- down-cell or https:/ /blueprints. launchpad. net/nova/ +spec/count- quota-usage- from-placement.
Even if we pre-determined which cells the project has instances in, if any of those cells are down then we're still not getting an accurate usage count if we're using the cell database. To pre-determine which cells a project has instances in, I think we could do that via the instance_mappings records in the nova_api database, maybe similar to how listing instances was modified with this change:
https:/ /review. openstack. org/#/c/ 509003/
The instance_mappings table doesn't have a user_id column so any quota we would need to count that involves a user_id would not work here though. This bug isn't specific about which quota is being calculated and when (server create or just when hitting the limits API?).