Closed lupen0120 closed 4 years ago
Changes Missing Coverage | Covered Lines | Changed/Added Lines | % | ||
---|---|---|---|---|---|
src/dashboard/server/api/controllers/team/cluster/metadata.js | 1 | 12 | 8.33% | ||
<!-- | Total: | 2 | 13 | 15.38% | --> |
Totals | |
---|---|
Change from base Build 3840: | -1.0% |
Covered Lines: | 1002 |
Relevant Lines: | 1083 |
Changes Missing Coverage | Covered Lines | Changed/Added Lines | % | ||
---|---|---|---|---|---|
src/dashboard/server/api/controllers/team/cluster/metadata.js | 1 | 12 | 8.33% | ||
<!-- | Total: | 2 | 13 | 15.38% | --> |
Totals | |
---|---|
Change from base Build 3840: | -1.0% |
Covered Lines: | 1002 |
Relevant Lines: | 1083 |
We want to have an Aether REST API, given team/cluster/userName, it could return #gpusPerNode and gpuType.
As the #gpusPerNode and gpuType would be quite different in different team/clusters, for example the resourceGpu in Azure-WestUS2-V100-16GB-LowPriority is 4; Azure-NorthCentralUS-V100 is 8. For our users, resourceGpu is the No.1 most frequently wrong parameter. When users switch team/cluster, lots of them don’t know they need to change resourceGpu as well.
for example:https://dltshub.redmond.corp.microsoft.com//api/teams/{$0}/clusters/{$1}/metadata?email={$2} the result is : {type: {$0}, per_node: {$1}}