feat: state endpoint #27
Merged
Conversation
This file contains 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
Problem: we want to be able to select a final cluster based on state Solution: while a cluster will likely send back state when accepting jobs, for the time being we are providing a one off endpoint for a cluster to send state data, and it requires the cluster to authenticate with the name and secret. For now the state date is key value pairs of compatibility metadata, and the values can be anything (interface) as we are expecting the selection algorithms that use them to know the type for a specific key. I will be added selection algorithms after this first stage that I intend to use in scheduler simulation - namely a post filter that serves as additional constraints that can be chosen (max jobs a cluster can accept and a cost value that can be minimized. Signed-off-by: vsoch <[email protected]>
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.
Problem: we want to be able to select a final cluster based on state Solution: while a cluster will likely send back state when accepting jobs, for the time being we are providing a one off endpoint for a cluster to send state data, and it requires the cluster to authenticate with the name and secret. For now the state date is key value pairs of compatibility metadata, and the values can be anything (interface) as we are expecting the selection algorithms that use them to know the type for a specific key. I will be added selection algorithms after this first stage that I intend to use in scheduler simulation - namely a post filter that serves as additional constraints that can be chosen (max jobs a cluster can accept and a cost value that can be minimized.