Absent a per-user quota for a resource, fall back to the per-project quota before default
Bug #1037590 reported by
Eoghan Glynn
This bug report is a duplicate of:
Bug #1034384: Quotas functionality seems broken in Nova.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Vish Ishaya |
Bug Description
Here are the semantics I expected of per-user quotas:
if a per-user quota is set for the current user:
bound their resource usage by that
elif a per-project quota set for the current project:
bound by that instead
else:
bound by the default quota
What we get in fact is a drop-thru' straight to the else clause, i.e. no fall-back on the per-project quota.
This would break if for example an F-2 install has some per-project quotas set, then upgrades to F-3, suddenly the old per-project quotas no longer apply (as there wouldn't be any per-user quotas set as yet).
Changed in nova: | |
assignee: | nobody → Eoghan Glynn (eglynn) |
Changed in nova: | |
status: | New → In Progress |
Changed in nova: | |
assignee: | Eoghan Glynn (eglynn) → Vish Ishaya (vishvananda) |
To post a comment you must log in.
Its straight-forward to over-ride the absent per-user quotas with the per-project threshold, however calculating the usage gets a bit intrusive into the DB code, as any quota having fallen back to per-project should be considered against the aggregate project usage (not just the usage for that individual user).