cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nitin Mehta (JIRA)" <>
Subject [jira] [Created] (CLOUDSTACK-4746) Allocation capacity of a cluster during HA
Date Thu, 26 Sep 2013 21:04:02 GMT
Nitin Mehta created CLOUDSTACK-4746:

             Summary: Allocation capacity of a cluster during HA
                 Key: CLOUDSTACK-4746
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
    Affects Versions: 4.2.0
            Reporter: Nitin Mehta
             Fix For: 4.2.1

When the host goes down. Cloudstack will stop the VM's for which HA is not enabled. Once cloudstack
marks these VM's as stopped then the capacity of these VM's is moved into the reserved capacity.
If the VM's are HA enabled then cloudstack will stop and start the VM's on another host. During
this time the capacity of the VM's will be moved to reserved capacity once the VM's are stopped,
But when the Vm's are being started cloudstack will try to calculate what will be total allocated
capacity if the VM is started again ( even though the CPU for the VM is already reserved).
This is a bug in cloudstack where the CPU required for the VM is considered twice when calculating
the allocated capacity.

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:

View raw message