[
https://issues.apache.org/jira/browse/CLOUDSTACK-4746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13799594#comment-13799594
]
ASF subversion and git services commented on CLOUDSTACK-4746:
-------------------------------------------------------------
Commit de28812addef186ad6740582d3e31b7d1609c058 in branch refs/heads/4.2 from
[~nitinme]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=de28812 ]
CLOUDSTACK-4746:
>From functionality point of view following will be changes.
-> Threshold will not be applied for vms undergoing HA process (say during host
going down event).
-> Threshold will not be applied for vms undergoing maintenance.
-> Threshold will apply for stop-start vm "after" the skip.counting.hours
(time till which we reserve the capacity for the stopped vm).
Reason being stop-start is a user initiated action and we are giving a time
window (skip.counting.hours) till which its guaranteed to start in the same
cluster.
After that time, threshold check applies bcz we still want to reserve the
capacity for urgent situations like HA, putting host into maintenance rather
than get it consumed in such user
initiated actions.
Signed off by : nitin mehta<[email protected]>
> Allocation capacity of a cluster during HA
> ------------------------------------------
>
> Key: CLOUDSTACK-4746
> URL: https://issues.apache.org/jira/browse/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
> Assignee: Nitin Mehta
> Priority: Critical
> 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 was sent by Atlassian JIRA
(v6.1#6144)
