[
https://issues.apache.org/jira/browse/CLOUDSTACK-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14165906#comment-14165906
]
ASF subversion and git services commented on CLOUDSTACK-6650:
-------------------------------------------------------------
Commit fbcab01ff02d30746a659fe7928c0ae9514237db in cloudstack's branch
refs/heads/master from [~amogh.vasekar]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=fbcab01 ]
Revert "CLOUDSTACK-6650: Reorder Cluster list in deployment planner to protect"
This reverts commit d910b4ff14bcf5d9e7892b5ffd39acb47745f106 since it is
causing encryption/decryption issues with RPM builds
> 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)
