fix: add Launchpad DMZ GH200 experience - #142
Open
aditsharma55 wants to merge 1 commit into
Open
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
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.
Fixes InsufficientCapacity failures when launching dmz.gh200x1.sxm on Launchpad. GH200 instances were failing even when GH200 capacity was available, because Brev requested the default amd64 Brev experience for arm64 GH200 hardware. Launchpad matches capacity against the experience's system_arch, found no amd64 GH200 nodes, and returned InsufficientCapacity despite ready arm64 GH200 capacity.
This change routes DMZ GH200 SXM instance types to the dedicated arm64 GH200 Launchpad experience.