[
https://issues.apache.org/jira/browse/CLOUDSTACK-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727371#comment-13727371
]
Bharat Kumar commented on CLOUDSTACK-1695:
------------------------------------------
The vms should be deployed only after the capacity recalculate to obey the
constraints.
if the VMs are deployed before the capacity calculation occurs the VM
deployment will not fail untill there is capacity on the host. however once
the capacity calculation is done the dash board will show that the usage is
greater than 100%
This is the behavior when the overcommit is changed dynamically.
> 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
> > > available 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.)
> Affects Versions: 4.2.0
> Environment: XEN,KVM Branch Master
> Reporter: prashant kumar mishra
> Assignee: Bharat Kumar
> Fix For: 4.2.0
>
> Attachments: DB_logs.rar, Logs_Db1245.rar, screenshot-1.jpg,
> screenshot-2.jpg
>
>
> 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
