wip: sidecar handler interface#28
Open
vsoch wants to merge 3 commits into
Open
Conversation
vsoch
force-pushed
the
add-sidecar-interface
branch
5 times, most recently
from
f538eab to
f7cd650
Compare
I want to support having other filters (extension points) running with fluence, which means that fluence might make a scheduling decision that is then rejected by some other plugin. If this happens we need to cancel the allocation and record the node names to give as constraints the next time around. This will likely take me a few days to work on, and I am thinking we want to replicate our original experiments in this paper to demosntrate the basic gang scheduling before we go into quantum / custom resources. Signed-off-by: vsoch <vsoch@users.noreply.github.com>
vsoch
force-pushed
the
add-sidecar-interface
branch
3 times, most recently
from
f9d1a71 to
58d73c9
Compare
vsoch
force-pushed
the
add-sidecar-interface
branch
3 times, most recently
from
9eb5c68 to
b96ddde
Compare
Signed-off-by: vsoch <vsoch@users.noreply.github.com>
vsoch
force-pushed
the
add-sidecar-interface
branch
2 times, most recently
from
9f1fa16 to
08bffaf
Compare
I do not like the leader worker design. Instead, lets move the sidecar logic into the handler (quantum specific) and allow for an entire group/gang (e.g., a minicluster/job/deployment or similar abstraction) to be the entire group ungated. We could not do this previously trying to split apart pods into leader worker, as they are derived from a common template. Signed-off-by: vsoch <vsoch@users.noreply.github.com>
vsoch
force-pushed
the
add-sidecar-interface
branch
from
08bffaf to
a17405b
Compare
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.
I want to support having other filters (extension points) running with fluence, which means that fluence might make a scheduling decision that is then rejected by some other plugin. If this happens we need to cancel the allocation and record the node names to give as constraints the next time around. This will likely take me a few days to work on, and I am thinking we want to replicate our original experiments in this paper to demosntrate the basic gang scheduling before we go into quantum / custom resources.