[
https://issues.apache.org/jira/browse/CLOUDSTACK-9650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15817894#comment-15817894
]
ASF GitHub Bot commented on CLOUDSTACK-9650:
--------------------------------------------
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1899
@koushik-das as a RM I want to ensure that all changes, irrespective of
their size, are merged after a QA process.
For UI/translation/docs changes tests are not necessary. Please understand
that it's difficult to review and keep track of each and every PR in detail,
and help and support from the community is appreciated to make this work. We
have agreed to gate the branches, and you've went ahead with merging without
following proper guidelines; testing against one hypervisor which have errors
that may/may-not be related to a PR are not good enough, given we've systems
like Trillian to test against at least three major hypervisors.
Lastly, I disagree, I think the setting should be available per zone for
admins to override this on a per-zone basis.
> 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)
