Respect fleet spec when provisioning on run apply#3022
Merged
Conversation
This was referenced Nov 14, 2025
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
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.
Closes #2969
This PR implements functions for combining fleet and run profiles and requirements so that process_submitted_jobs respects both fleet and run specs when provisioning new instances. If fleet spec and run spec are not compatible / have empty intersection – job is terminated with FAILED_TO_START_DUE_TO_NO_CAPACITY. Run plan offers are not affected by this PR and do not respect fleet spec – to keep
dstack offerslogic intact and because run plan offers will be different for different fleets. We may introduce per-fleet offers in run plan after #3021 and #3020.Example: respect fleet backend