Move all prod capacity reservation IDs into clusters.yaml#587
Open
huydhn wants to merge 3 commits into
Open
Conversation
This was referenced May 16, 2026
tofu plan — arc-cbr-production✅ Plan succeeded · commit Plan output |
jeanschmidt
approved these changes
May 17, 2026
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
2 participants
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.
Stack from ghstack (oldest at bottom):
Both prod clusters now declare their capacity_reservation_ids in
clusters.yaml instead of inside the shared module def files. The def
files describe nodepool shape; clusters.yaml declares per-cluster
reservations.
Moved out of def files into clusters.arc-cbr-production:
nodepools-h100: cr-0c3f05dffb85ed832
nodepools-b200: cr-02cf82c9a0f7fa8c0, cr-06ec9d6c14b9d9981
Added under clusters.arc-cbr-production-uw1:
nodepools-h100: cr-04d3d1d84e127a562 (2 × p5.48xlarge, 16 H100 GPUs)
cr-09a53051589034fb8 (4 × p5.48xlarge, 32 H100 GPUs)
Future capacity-reservation rotations now touch clusters.yaml only,
keeping the reservation lifecycle next to the cluster config rather
than buried inside shared module data. The generator change in the
previous commit reads these values via the
NODEPOOLS_CAPACITY_RESERVATION_IDS_OVERRIDE env var that the nodepools
deploy.sh now exports per cluster.