[
https://issues.apache.org/jira/browse/CLOUDSTACK-9650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15814464#comment-15814464
]
ASF subversion and git services commented on CLOUDSTACK-9650:
-------------------------------------------------------------
Commit 97ffe0711ec3abbadda01b1c92ca050fe4cac59e in cloudstack's branch
refs/heads/master from [~koushikd]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=97ffe07 ]
CLOUDSTACK-9650: Allow starting VMs regardless of cpu/memory
cluster.disablethreshold setting
Introduced a global configuration flag 'cluster.threshold.enabled'. By default
the flag is true.
If the value is false, then a VM can be started in a cluster even if the
cluster thresholds are
crossed. However, for a new VM deployment the cluster threshold will always be
honoured.
> Allow starting VMs regardless of cpu/memory cluster.disablethreshold setting
> ----------------------------------------------------------------------------
>
> Key: CLOUDSTACK-9650
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9650
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.10.0.0
> Reporter: Koushik Das
> Assignee: Koushik Das
> Fix For: 4.10.1.0
>
>
> VM deployments are not allowed on clusters where resource (cpu/memory)
> allocation has exceeded the cluster disabled thresholds. The same policy also
> gets applied in case of start VM if last host where the VM was running
> doesn't have enough capacity and a new host is picked up. In certain
> scenarios this can be restrictive and despite having capacity, the VM cannot
> be started.
> This improvement is to provide administrator an option to disable/enable
> cluster threshold enforcement during start of a stopped VM as long as
> sufficient capacity is available.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
