docs: add generic xpu topology-aware scheduling design - #5965
miantalha45 wants to merge 4 commits into
Conversation
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Signed-off-by: Talha Amjad <myown4500@gmail.com>
ad7b82c to
3269577
Compare
devzizu
left a comment
There was a problem hiding this comment.
Thanks for this @miantalha45‚it's a serious piece of work, and the level of detail is well beyond what I expected at this stage. I've done a first pass and left comments inline, but I still have some sections to go through in the next few days.
Align the topology view with SchedulerCache snapshots, clarify provider and canonical identity contracts, define policy lifecycle and failure reporting, and refine compact allocation behavior. Signed-off-by: Talha Amjad <myown4500@gmail.com>
|
thank you so much @devzizu for this detailed review. I have addressed all your comments and also made a lot of changes in document. Kindly have a look on it again now. |
Signed-off-by: Talha Amjad <myown4500@gmail.com>
Signed-off-by: Talha Amjad <myown4500@gmail.com>
|
Hi @JesseStutler @hajnalmt @devzizu @wangyang0616 |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
Adds a design proposal for generic xPU topology-aware scheduling in Volcano.
It defines the proposed topology provider, canonical topology cache, workload API, scheduling behavior, adapter contract, readiness and freshness handling, security model, compatibility boundaries, rollout plan, and validation strategy.
AI assistance was used to help structure and edit this design document. I reviewed the final content and take responsibility for it.
Which issue(s) this PR fixes:
Related to #5751
Special notes for your reviewer:
Does this PR introduce a user-facing change?