[
https://issues.apache.org/jira/browse/CLOUDSTACK-9650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15715791#comment-15715791
]
ASF GitHub Bot commented on CLOUDSTACK-9650:
--------------------------------------------
GitHub user koushik-das opened a pull request:
https://github.com/apache/cloudstack/pull/1812
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.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/koushik-das/cloudstack CLOUDSTACK-9650
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1812.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1812
----
commit 97ffe0711ec3abbadda01b1c92ca050fe4cac59e
Author: Koushik Das <kous...@apache.org>
Date: 2016-12-02T17:38:32Z
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)
