Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 2 Oct 2014 21:04:34 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12713828.1399959484000.179132.1412283874669@Atlassian.JIRA>
In-Reply-To: <JIRA.12713828.1399959484000@Atlassian.JIRA>
References: <JIRA.12713828.1399959484000@Atlassian.JIRA>
 <JIRA.12713828.1399959484513@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-6650) Reorder Cluster list in
 deployment planner to protect GPU enabled hosts from non-GPU VM deployment
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14157183#comment-14157183 ] 

ASF subversion and git services commented on CLOUDSTACK-6650:
-------------------------------------------------------------

Commit 0ef6cd36c456cb76efd9f7acea988c40d72b1bd8 in cloudstack's branch refs/heads/master from [~amogh.vasekar]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0ef6cd3 ]

Revert "CLOUDSTACK-6650: Reorder Cluster list in deployment planner to protect"

This reverts commit 39fe766c2b6fb6edd4c1bf828625b29d9bb87719.


> Reorder Cluster list in deployment planner to protect GPU enabled hosts from non-GPU VM deployment
> --------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-6650
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6650
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>         Environment: MS 4.4
> XS 620SP1
>            Reporter: Sanjay Tripathi
>            Assignee: Sanjay Tripathi
>             Fix For: 4.4.0
>
>
> If CS environment has GPU cards then for non-GPU enabled VM deployments, deployment planner should check the non-GPU hosts first and if they are out of capacity then deploy in  GPU enabled hosts.
> For now, this restriction is imposed at cluster level not at zone level, so to protect GPU resources, CS should give lower priority to clusters which has GPU enabled host and high priority to clusters which contains non-GPU enabled hosts.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)