feat: scheduler (10/): add more scheduler framework logic #391
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
I am closing this PR as recent design changes have made this PR obsolete. New ones will be sent soon when the API change is finalized. |
weng271190436
pushed a commit
that referenced
this pull request
Jan 6, 2026
Signed-off-by: Wantong Jiang <wantjian@microsoft.com>
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of your changes
This PR is part of the PRs that implement the Fleet workload scheduling.
It features parts of the scheduler framework logic.
I have:
make reviewableto ensure this PR is ready for review.How has this code been tested
Special notes for your reviewer
This PR includes contents from some unmerged PRs, it will be rebased after the prerequisite PRs are merged.
Please note that changes made on earlier PRs will not be picked here automatically unless the PR is explicitly rebased.
Per earlier agreements, testing on this PR has a limited focus/scope.