cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "bharat kumar" <bharat.ku...@citrix.com>
Subject Re: Review Request 12967: Not enough cpu avialable in cluster according to new overcommit ratio but all stopped Vms can be started without any failure
Date Wed, 31 Jul 2013 09:54:11 GMT

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/12967/
-----------------------------------------------------------

(Updated July 31, 2013, 9:54 a.m.)


Review request for cloudstack, Kishan Kavala and Nitin Mehta.


Changes
-------

revision 3 is for 4.2 revision 4 is for master.


Bugs: Cloudstack-1695


Repository: cloudstack-git


Description
-------

https://issues.apache.org/jira/browse/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 >> available cpu )


Diffs (updated)
-----

  server/src/com/cloud/capacity/CapacityManagerImpl.java 05a47dd 
  server/src/com/cloud/vm/VirtualMachineManagerImpl.java 1fb118f 

Diff: https://reviews.apache.org/r/12967/diff/


Testing
-------

Tested on old master.
This happened because we were not recalculating the used and the reserved capacities based
on the new overcommit ratio. 

Now used and reserved capacities of all the hosts in a overcommited cluster will be recalculated
on overcommit change by the capacity checker. However this will happen only when capacity
checker runs meaning the change in capacities due to updated overcommit values will not be
instantaneous.
  


Thanks,

bharat kumar


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message