Drop hardcoded Hot Aisle VM specs #3239
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
Use the spec object from gpuhunt offers instead. This allows newly added instance types with different CPU, RAM, disk, and GPU count configurations to automatically become available in dstack. However, limit the supported GPUs to MI300X, since other GPUs and CPU-only VMs might need to be tested by the dstack team before they become available to users.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Use the spec object from gpuhunt offers instead.
This allows newly added instance types with
different CPU, RAM, disk, and GPU count
configurations to automatically become available
in dstack. However, limit the supported GPUs to
MI300X, since other GPUs and CPU-only VMs might
need to be tested by the dstack team before they
become available to users.
See also dstackai/gpuhunt#194
Before merging: