microsoft / microsoft/pai

Update hived request generation in rest-server

Open
#5,419 0 comments 0 reactions 1 assignee View on GitHub

@hzy46 is already working on this.

Since Apr 12, 2021.

Dominant language
JavaScript
Stars
2.7k
Forks
554
Avg merge
20h 42m
Merged PRs (30d)
14

Description

new schema in OpenPAI job protocol:

extras:
  gangAllocation: true/false
  hivedscheduler:
    jobPriorityClass: crit | prod | test (default) | oppo
    taskRoles:
     <taskrole_name>:
        pinnedCellId: string | null (default)
        # if resourcePerInstance doesn't exist, we should calculate it from 
        # config.taskroles.<taskrole_name>.resourcePerInstance, and use null as skuType
        resourcePerInstance:
          skuNum: number 
          skuType: string | null (default)
       withinOne: string | null (default)
    taskRoleGroups:
        # we don't allow single group: length of taskRoles must be > 1 
        # we don't allow overlap
      - taskRoles: [master, worker]
         withinOne: string | null

Remaining question:

  • will extras.gangAllocation have any effect? - use the same behavior as before
  • should we modify api/v2/cluster/sku-types - should provide a new api which returns all cell chain
  • IgnoreK8sSuggestedNodes?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.