[jira] [Commented] (CLOUDSTACK-6650) Reorder Cluster list in deployment planner to protect GPU enabled hosts from non-GPU VM deployment
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14154700#comment-14154700 ] ASF subversion and git services commented on CLOUDSTACK-6650: - Commit 39fe766c2b6fb6edd4c1bf828625b29d9bb87719 in cloudstack's branch refs/heads/master from [~sanjay.tripathi] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=39fe766 ] CLOUDSTACK-6650: Reorder Cluster list in deployment planner to protect GPU enabled hosts from non-GPU VM deployment. Cluster reordering is based on the number of unique host tags in a cluster, cluster with most number of unique host tags will put at the end of list. Hosts with GPU capability will get tagged with implicit tags defined by global config param 'implicit.host.tags' at the time os host discovery. Also added FirstFitPlannerTest unit test file. > 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)
[jira] [Commented] (CLOUDSTACK-6650) Reorder Cluster list in deployment planner to protect GPU enabled hosts from non-GPU VM deployment
[ 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)
[jira] [Commented] (CLOUDSTACK-6650) Reorder Cluster list in deployment planner to protect GPU enabled hosts from non-GPU VM deployment
[ 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)
[jira] [Commented] (CLOUDSTACK-6650) Reorder Cluster list in deployment planner to protect GPU enabled hosts from non-GPU VM deployment
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161770#comment-14161770 ] ASF subversion and git services commented on CLOUDSTACK-6650: - Commit d910b4ff14bcf5d9e7892b5ffd39acb47745f106 in cloudstack's branch refs/heads/master from [~sanjay.tripathi] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d910b4f ] CLOUDSTACK-6650: Reorder Cluster list in deployment planner to protect GPU enabled hosts from non-GPU VM deployment. Cluster reordering is based on the number of unique host tags in a cluster, cluster with most number of unique host tags will put at the end of list. Hosts with GPU capability will get tagged with implicit tags defined by global config param 'implicit.host.tags' at the time os host discovery. Also added FirstFitPlannerTest unit test file. > 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)
[jira] [Commented] (CLOUDSTACK-6650) Reorder Cluster list in deployment planner to protect GPU enabled hosts from non-GPU VM deployment
[ 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)
[jira] [Commented] (CLOUDSTACK-6650) Reorder Cluster list in deployment planner to protect GPU enabled hosts from non-GPU VM deployment
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14170848#comment-14170848 ] ASF subversion and git services commented on CLOUDSTACK-6650: - Commit e4a8bbcdf42bd3133e5cb7e3230b45c0e7018426 in cloudstack's branch refs/heads/master from [~sanjay.tripathi] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e4a8bbc ] CLOUDSTACK-6650: Reorder Cluster list in deployment planner to protect GPU enabled hosts from non-GPU VM deployment. Cluster reordering is based on the number of unique host tags in a cluster, cluster with most number of unique host tags will put at the end of list. Hosts with GPU capability will get tagged with implicit tags defined by global config param 'implicit.host.tags' at the time os host discovery. Also added FirstFitPlannerTest unit test file. > 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)
[jira] [Commented] (CLOUDSTACK-6650) Reorder Cluster list in deployment planner to protect GPU enabled hosts from non-GPU VM deployment
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14170850#comment-14170850 ] ASF subversion and git services commented on CLOUDSTACK-6650: - Commit 176e0d47bb86fcc4ab0cdb33f95f73d751f2d814 in cloudstack's branch refs/heads/4.5 from [~sanjay.tripathi] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=176e0d4 ] CLOUDSTACK-6650: Reorder Cluster list in deployment planner to protect GPU enabled hosts from non-GPU VM deployment. Cluster reordering is based on the number of unique host tags in a cluster, cluster with most number of unique host tags will put at the end of list. Hosts with GPU capability will get tagged with implicit tags defined by global config param 'implicit.host.tags' at the time os host discovery. Also added FirstFitPlannerTest unit test file. > 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)
