Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

wip: add constraint select algorithm #29

Merged
merged 6 commits into from Apr 8, 2024
Merged

Conversation

vsoch
Copy link
Member

@vsoch vsoch commented Apr 7, 2024

This will be a PR over the next several days (pending on when I get power back, I'm tethered to my work phone sitting in my car to open this 馃槶 ) that has what we need for the next round of experiments. Specifically:

  • Support for cluster state (additional metadata a cluster can provide about state to inform selection)
  • Support for constraint matching that uses this state (and a new constraints algorithm)
  • A new match algorithm that allows for using either equals or range Support for multiple match algorithms in one job spec 聽#28

Our ETA on power is tomorrow, and that's the earliest, so I'm probably going to focus on staying alive for the next few days, but it's not that bad to sit in the car and do bits of work. It still kind of sucks though. 馃槩

I do have cool experiments underway, just 5x slower than I would have been with power, will hopefully be able to get them done and shared soon.

insert Monty Python I'm not dead yet

Problem: we need to be able to have more complex selection logic
Solution: prototype constraint selection algorithm
Signed-off-by: vsoch <vsoch@users.noreply.github.com>
Problem: a constraint needs to be able to run arbitrary filters
Solution: implement the constraint->step->filter step!
Signed-off-by: vsoch <vsoch@users.noreply.github.com>
Signed-off-by: vsoch <vsoch@users.noreply.github.com>
Problem: we need to be able to select a different selection
algorithm on job submit, because one might require variables
that are not present.
Solution: add the selection_algorithm to the submit job
endpoint.

Signed-off-by: vsoch <vsoch@users.noreply.github.com>
Problem: most people will want to match a combination of range
and equality. They should be under one place.
Solution: update the match algorithm to be a superset of
two algorithms specific to this, range and equals.
It really sucks without power, sad dinosaur :(

Signed-off-by: vsoch <vsoch@users.noreply.github.com>
Signed-off-by: vsoch <vsoch@users.noreply.github.com>
@vsoch vsoch merged commit 8fc1896 into main Apr 8, 2024
3 checks passed
@vsoch vsoch deleted the add-constraint-select-algorithm branch April 8, 2024 20:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant