[ https://issues.apache.org/jira/browse/CLOUDSTACK-9650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15817422#comment-15817422 ]
ASF subversion and git services commented on CLOUDSTACK-9650: ------------------------------------------------------------- Commit 729ae6d186786b8b7c79a99bb7a769fff93e399b in cloudstack's branch refs/heads/master from [~koushikd] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=729ae6d ] Merge pull request #1899 from Accelerite/CLOUDSTACK-9650 CLOUDSTACK-9650: Allow starting VMs regardless of cpu/memory cluster.disablethreshold setting Fixed the scope of configuration flag 'cluster.threshold.enabled' introduced as part of PR#1812 to global * pr/1899: CLOUDSTACK-9650: Allow starting VMs regardless of cpu/memory cluster.disablethreshold setting Signed-off-by: Koushik Das <kous...@apache.org> > 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)