docs: add HCP scheduling controller design - #6649
Draft
Gerd Oberlechner (geoberle) wants to merge 3 commits into
Draft
docs: add HCP scheduling controller design#6649Gerd Oberlechner (geoberle) wants to merge 3 commits into
Gerd Oberlechner (geoberle) wants to merge 3 commits into
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: geoberle The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Skipping CI for Draft Pull Request. |
Gerd Oberlechner (geoberle)
force-pushed
the
hcp-scheduling
branch
from
August 21, 2026 15:28
8dc4467 to
9cd624b
Compare
Move HCP placement decisions from Cluster Service into the backend. Split into three phases: simple placement with provision shard pinning, capacity-aware scheduling with pending lists, and observation-based pending cleanup via CapacityReport resource ID mirroring.
Gerd Oberlechner (geoberle)
force-pushed
the
hcp-scheduling
branch
from
August 21, 2026 16:50
9cd624b to
935acc8
Compare
…lout Replaces the original 3-phase design (simple SPC-count → capacity-aware → observation-based cleanup) with a revised phasing that delivers capacity-aware scheduling from the first placement phase: - Phase 0: Mirror ReadyResourceIDs/NotReadyResourceIDs from CapacityReport to ManagementClusterScheduling.Status. Pure data plumbing. - Phase 1: Swift-NIC scheduling against ScaleCeiling with pending reservations. Two-path cleanup: CapacityReportingController clears observed entries, PendingCleanupController sweeps stale entries. ManagementClusterPlacementSync detects and self-heals CS pinning mismatches. - Phase 2: Multi-resource capacity-aware fit with HCPResourceRequirements. Key design changes from the original phasing: - SPC Spec/Status split: Spec = scheduler intent, Status = CS-confirmed reality. Mismatch triggers error log and Spec overwrite for self-healing. - PendingAssignedClusters introduced in phase 1 (was phase 2). - No explicit assignedClusters field — ReadyResourceIDs ∪ NotReadyResourceIDs serves that role. - Provision shard pinning via ClusterBuilder.ProvisionShardID() SDK method.
Align the Spec/Status mismatch description with the actual behavior (log error + overwrite Spec with Status to self-heal) and replace the PR Azure#6651 reference with a self-contained implementation description.
Gerd Oberlechner (geoberle)
force-pushed
the
hcp-scheduling
branch
from
August 25, 2026 13:59
38dee60 to
1c50794
Compare
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
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.
Summary
Test plan