Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C6DDC10806 for ; Tue, 5 Nov 2013 00:46:18 +0000 (UTC) Received: (qmail 82746 invoked by uid 500); 5 Nov 2013 00:46:18 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 82723 invoked by uid 500); 5 Nov 2013 00:46:18 -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 82716 invoked by uid 500); 5 Nov 2013 00:46:18 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 82713 invoked by uid 99); 5 Nov 2013 00:46:18 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Nov 2013 00:46:18 +0000 Date: Tue, 5 Nov 2013 00:46:18 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-4948) DeploymentPlanner: Logic to check if cluster can be avoided, needs to consider if VM is using local storage and/or shared storage MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-4948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13813480#comment-13813480 ] ASF subversion and git services commented on CLOUDSTACK-4948: ------------------------------------------------------------- Commit 4be79472819d6100579a44fee71253ab54766713 in branch refs/heads/master from [~prachidamle] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4be7947 ] CLOUDSTACK-4948: DeploymentPlanner: Logic to check if cluster can be avoided, needs to consider if VM is using local storage and/or shared storage Changes: - Consider if VM requires the local storage or shared storage or both for its disks. - Accordingly all pools in the cluster should consider local or shared or both pools Conflicts: server/src/com/cloud/agent/manager/allocator/HostAllocator.java > DeploymentPlanner: Logic to check if cluster can be avoided, needs to consider if VM is using local storage and/or shared storage > --------------------------------------------------------------------------------------------------------------------------------- > > Key: CLOUDSTACK-4948 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4948 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: Management Server > Affects Versions: 4.2.0 > Reporter: Prachi Damle > Assignee: Prachi Damle > Fix For: 4.2.1 > > > During VM deployment the DeploymentPlanningManager iterates over each cluster and if there is no destination found in a cluster, it tries to see if that cluster should be avoided. > This logic puts a cluster is avoid set if all hosts in the cluster are in avoid set or all pools in the cluster are in avoid set. > In the check to see all pools, the logic should consider the storage requirements of the VM. If the VM just uses local storage, 'all pools' in cluster should only consider local pools in the cluster. Else the presence of shared pools in the cluster can prevent the cluster from getting avoided. -- This message was sent by Atlassian JIRA (v6.1#6144)