[
https://issues.apache.org/jira/browse/CLOUDSTACK-8438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14522873#comment-14522873
]
ASF subversion and git services commented on CLOUDSTACK-8438:
-------------------------------------------------------------
Commit 3100fc15544bd5bdbe8d2eb0a0e429355657b910 in cloudstack's branch
refs/heads/master from [~koushikd]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3100fc1 ]
CLOUDSTACK-8438: Proper enforcement of hypervisor capability "max. guest limit"
VMs in transition states - Starting, Stopping, Migrating - are also taken into
account for enforcing "max. guest limit"
> Proper enforcement of hypervisor capability "max. guest limit"
> --------------------------------------------------------------
>
> Key: CLOUDSTACK-8438
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8438
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.5.0
> Reporter: Koushik Das
> Assignee: Koushik Das
> Fix For: 4.6.0
>
>
> Currently only the VMs in 'Running' state are considered for enforcing "max.
> guest limit". There is a flaw in this approach. If there are parallel VM
> deployments happening then there is a possibility that the HV host may end up
> having more VMs than the limit.
> Fix would be consider VMs in transition states as well for enforcing limit.
> These are Starting, Stopping, Migrating.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
