cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "prashant kumar mishra (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-1695) Not enough cpu avialable in cluster according to new overcommit ratio but all stopped Vms can be started without any failure(required cpu for stopped vm is > > availble cpu )
Date Mon, 18 Mar 2013 05:50:15 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

prashant kumar mishra updated CLOUDSTACK-1695:
----------------------------------------------

    Description: 
After Stop/Destroy , vms can be successfully start/Restore-start  only when enough resources
are available based on current overcommit ratio, .

Step to Reproduce
-----------------------------
1-Set cpu overcommit ratio to 4
2-Deploy vms such that no cpu left in cluster
3-change overcommit ratio to 1
4-Stop/Destroy all the vms
5-Start/restore-start all vms

Expected Result
-------------------------
only few vms should come up ,since there is  less resource(overcommit ratio=1) available 
than before (when overcommit ratio was 4)

Actual
----------------
All vm stopped/Destroyed  in step 4 came up without any failure


  was:
After Stop/Destroy , vms can be successfully start/Restore-start  only when enough resources
are available based on current overcommit ratio, .

Step to Reproduce
-----------------------------
1-Set cpu overcommit ratio to 4
2-Deploy vms such that no cpu left in cluster
3-change overcommit ratio to 1
4-Stop/Destroy all the vms
5-Start/restore-start all vms

Expected Result
-------------------------
only few vms should come up ,since there is  less resource(overcommit ratio=1) available 
than before (when overcommit ratio was 4)

Actual
----------------
All vm stopped/Destroyed  in step 4 came up without failure


    
> Not enough cpu avialable in cluster according to new overcommit ratio but all stopped
Vms can be started without any failure(required cpu for stopped vm is > > availble cpu
)
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1695
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1695
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: prashant kumar mishra
>            Assignee: Bharat Kumar
>
> After Stop/Destroy , vms can be successfully start/Restore-start  only when enough resources
are available based on current overcommit ratio, .
> Step to Reproduce
> -----------------------------
> 1-Set cpu overcommit ratio to 4
> 2-Deploy vms such that no cpu left in cluster
> 3-change overcommit ratio to 1
> 4-Stop/Destroy all the vms
> 5-Start/restore-start all vms
> Expected Result
> -------------------------
> only few vms should come up ,since there is  less resource(overcommit ratio=1) available
 than before (when overcommit ratio was 4)
> Actual
> ----------------
> All vm stopped/Destroyed  in step 4 came up without any failure

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message