salvatore e10b008f7a Do not track active reservations ... Reservations have a transient nature: a reservation lifespan typically begins and ends with a single request. Therefore tracking reserved amounts for each tenant and resource is not nearly as efficient as tracking resource usage. Indeed it is fairly easy to verify that the overhead for tracking reserved amounts is much greater than the one needed for counting active reservations for each tenant and resource. This patch removes the logic for tracking reservations, and replaces it with an explicit count of active reservations. Please note that this patch does not adjust accordingly the ResourceUsage DB model. This will be done in a separate patch with an expand migration; this should avoid most merge conflicts before the final patch for restoring reservation logic merges. Related-Blueprint: better-quotas Change-Id: Ib5e3bd61c1bc0fc8a5d612dae5c1740a8834a980		2015-09-02 01:42:14 +00:00
..
__init__.py	Reservations support	2015-08-17 15:54:19 -07:00
resource.py	Do not track active reservations	2015-09-02 01:42:14 +00:00
resource_registry.py	Merge "Minor typo fix"	2015-08-20 11:03:33 +00:00