Bug 1264420 - quota consistence across the projects
quota consistence across the projects
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova (Show other bugs)
7.0 (Kilo)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: 8.0 (Liberty)
Assigned To: Eoghan Glynn
Depends On:
  Show dependency treegraph
Reported: 2015-09-18 08:30 EDT by Pablo Caruana
Modified: 2015-09-25 09:04 EDT (History)
12 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-09-25 09:04:27 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 1467560 None None None Never

  None (edit)
Description Pablo Caruana 2015-09-18 08:30:53 EDT
When deploying stack from heat notice some  nova.usages and cinder.usages.

In short is a know limitation on the code and the database schema and hope this can give a better understanding when we take a look both nova.instances, nova.quota_usages and  cinder.quota_usages

from that point there are two things to resolve, the  database tables inconsistencies  between and inside nova,cinder and neutron protects and potential RFE for covering code and/or potential db schemas.

From what Already researched this looks is a know issue in Openstack tables at least from nova as nova.usages not tracking the uuid for the instance uuid consuming the quota and if removed from the hypervisor, leaving  you to a manual comparison.
Comment 5 Eoghan Glynn 2015-09-25 09:04:27 EDT
The internal database schema for nova and cinder are not considered a user-visible API or contract. Instead, these are considered a private implementation detail.

Also, these schema are not maintained in a cross-project way aiming for consistency (unlike how say the API working group attempts to acheive cross-project consistency on the public REST APIs).

So, making these database schema consistent is not something we can commit to doing.

Note You need to log in before you can comment on or make changes to this bug.