Bug 786344

Summary: Cloud quota not enforced for multi-instance deployment.
Product: [Retired] CloudForms Cloud Engine Reporter: Aziza Karol <akarol>
Component: aeolus-conductorAssignee: Shveta <ssachdev>
Status: CLOSED ERRATA QA Contact: wes hayutin <whayutin>
Severity: high Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, athomas, deltacloud-maint, hbrock, ssachdev
Target Milestone: beta   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-15 22:25:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
cloud quota
none
quota for multi assembly deployment none

Description Aziza Karol 2012-02-01 06:53:51 UTC 
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
I enforced cloud quota such a way that only 1 instance can be launched out of 2 instances from muti-instance deployable.
so while launching the deployment, 1 instances should get launched and for the second one it should display "cloud quota reached".

But this does not happen.Both the instances are getting launched.it seems cloud  quota is not checked while launching multi instance deployment.

see attached screenshot.

Note:
cloud quota is checked for single instance deployment and displays message " cloud quota reached" which is correct.
  


Expected results:
Cloud quota should be enforced for multi-instance deployment.

Additional info:
rpm -qa | grep aeolus
aeolus-conductor-0.8.0-17.el6.noarch
rubygem-aeolus-cli-0.3.0-7.el6.noarch
aeolus-configure-2.5.0-11.el6.noarch
aeolus-conductor-daemons-0.8.0-17.el6.noarch
aeolus-all-0.8.0-17.el6.noarch
aeolus-conductor-doc-0.8.0-17.el6.noarch
rubygem-aeolus-image-0.3.0-7.el6.noarch
Comment 1 Aziza Karol 2012-02-01 06:54:19 UTC 
Created attachment 558760 [details]
cloud quota
Comment 2 Angus Thomas 2012-02-02 13:50:29 UTC 
The solution for this is to check the quota before launch, and if there isn't sufficient quota remaining to launch all of the instances defined in the deployable, not to launch the deployable at all.

Partially launching the deployable, by starting as many instances as the quota permits, would be likely to leave the user with a non-functional deployment.
Comment 3 Tzu-Mainn Chen 2012-02-02 16:55:58 UTC 
Patch created; it prevents multi-instance deployables from launching at all if doing so would go over the pool/pool family quota:

https://fedorahosted.org/pipermail/aeolus-devel/2012-February/008593.html
Comment 4 Tzu-Mainn Chen 2012-02-03 15:02:57 UTC 
Pushed to 1.0-staging:

commit 78cbf85d6de7bdfe5c26a417b580cdd9c829efb8
BZ 786344 added pre-launch validation for multi-instance deployments
Comment 5 Shveta 2012-02-23 13:25:41 UTC 
Created attachment 565301 [details]
quota for multi assembly deployment

Before launching quota is checked for multi assembly deployment

rpm -qa|grep aeolus
aeolus-conductor-0.8.0-35.el6.noarch
rubygem-aeolus-cli-0.3.0-10.el6.noarch
aeolus-conductor-doc-0.8.0-35.el6.noarch
rubygem-aeolus-image-0.3.0-9.el6.noarch
aeolus-all-0.8.0-35.el6.noarch
aeolus-conductor-daemons-0.8.0-35.el6.noarch
aeolus-configure-2.5.0-15.el6.noarch
Comment 6 errata-xmlrpc 2012-05-15 22:25:59 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2012-0583.html