You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Koushik Das (JIRA)" <ji...@apache.org> on 2017/01/10 09:33:58 UTC
[jira] [Resolved] (CLOUDSTACK-9650) Allow starting VMs regardless
of cpu/memory cluster.disablethreshold setting
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Koushik Das resolved CLOUDSTACK-9650.
-------------------------------------
Resolution: Fixed
> 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)