Bug 803791 - Cloud Resource Zone Quota calculations look off when is quota reduced after instances are launched
Cloud Resource Zone Quota calculations look off when is quota reduced after i...
Status: NEW
Product: CloudForms Cloud Engine
Classification: Red Hat
Component: aeolus-conductor (Show other bugs)
Unspecified Linux
unspecified Severity medium
: rc
: ---
Assigned To: Angus Thomas
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2012-03-15 12:24 EDT by Ronelle Landy
Modified: 2014-01-05 13:36 EST (History)
6 users (show)

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

Attachments (Terms of Use)
Quota calculation (198.25 KB, image/png)
2012-03-15 12:26 EDT, Ronelle Landy
no flags Details

  None (edit)
Description Ronelle Landy 2012-03-15 12:24:50 EDT
Description of problem:

I launched 318 instances to the mock provider using the default Could Resource Zone. Afterwards, I edited the zone to reduce the quota to 300. (I was looking to see if conductor would shut down my excess instances). Conductor left all instances up and running but the quota calculations in conductor/pools page look a little strange ( albeit mathematically correct):

Pool Quota Used
    318 of -18

(see attached screenshot)

Steps to Reproduce:
1. Launch a number of instances into conductor
2. Edit the cloud resource zone to limit the number of instances to less than the number of instances launched
3. Go back to the conductor/pools page and see the Pool Quota Used calculation

rpms tested:

rpm -qa |grep aeolus
Comment 1 Ronelle Landy 2012-03-15 12:26:48 EDT
Created attachment 570346 [details]
Quota calculation
Comment 2 Scott Seago 2012-03-15 19:17:41 EDT
I don't think it's in scope to shut down instances automatically when quota is reduced -- we don't have any way of knowing which ones should be shut down, and it's not obvious to me that automatically shutting down instances is even desirable. Still, having "-18" available is obviously wrong. I think there are two stages to the fix:

1) stage 1, to close this bug:
  a) Fix the "availability" to show "0" available instead of a negative number. 
  b) If quota used is > 100% perhaps we should make it bold/red/etc? 
  c) Possibly with an alert message "You are currently over quota".

If this is implemented as a 1.0 blocker, doing a) alone may be sufficient.

2) stage 2, later (1.1?):
  Any time a quota is modified that would put it overallocation (i.e. moving the number below current usage) -- for whatever level (user, pool/zone, environment/cloud, provider account), we should warn the admin/user that the quota will be exceeded, but that no instances/applications will be shut down, allowing the admin to do it anyway.
Comment 3 Hugh Brock 2012-03-19 13:32:41 EDT
Agree with the proposed fix, but don't believe it is a blocker. Moving to 1.1.

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