Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 6C86E200C09 for ; Tue, 10 Jan 2017 11:12:00 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 6B33D160B31; Tue, 10 Jan 2017 10:12:00 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id BCA4F160B3D for ; Tue, 10 Jan 2017 11:11:59 +0100 (CET) Received: (qmail 21319 invoked by uid 500); 10 Jan 2017 10:11:58 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 21211 invoked by uid 500); 10 Jan 2017 10:11:58 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 21176 invoked by uid 99); 10 Jan 2017 10:11:58 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Jan 2017 10:11:58 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 881192C2A6C for ; Tue, 10 Jan 2017 10:11:58 +0000 (UTC) Date: Tue, 10 Jan 2017 10:11:58 +0000 (UTC) From: "Koushik Das (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-9650) Allow starting VMs regardless of cpu/memory cluster.disablethreshold setting MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 10 Jan 2017 10:12:00 -0000 [ https://issues.apache.org/jira/browse/CLOUDSTACK-9650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15814567#comment-15814567 ] Koushik Das commented on CLOUDSTACK-9650: ----------------------------------------- Thanks [~ustcweizhou@gmail.com] for pointing it out, the config is meant to be a global one. I will create a PR to fix it. > 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)