cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohit Yadav (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-6650) Reorder Cluster list in deployment planner to protect GPU enabled hosts from non-GPU VM deployment
Date Wed, 01 Oct 2014 20:47:34 GMT

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

Rohit Yadav commented on CLOUDSTACK-6650:
-----------------------------------------

The fix for this build breaks a test and in turn master, please fix it. It's a good idea to
make use of TravisCI or Github PR in case you don't have time/resources to build/test locally
before you push code to maser.

> 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)

Mime
View raw message