-
Notifications
You must be signed in to change notification settings - Fork 32
β¨ Adding generic scheduling capability to dynamic-scheduler [part 1/2] #8307
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βll occasionally send you account related emails.
Already on GitHub? Sign in to your account
β¨ Adding generic scheduling capability to dynamic-scheduler [part 1/2] #8307
Conversation
Codecov Reportβ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## master #8307 +/- ##
==========================================
+ Coverage 87.83% 87.92% +0.09%
==========================================
Files 1964 1976 +12
Lines 76341 77220 +879
Branches 1342 1342
==========================================
+ Hits 67051 67897 +846
- Misses 8886 8919 +33
Partials 404 404
Continue to review full report in Codecov by Sentry.
π New features to boost your workflow:
|
π§ͺ CI InsightsHere's what we observed from your CI run for 6d78813. β Passed Jobs With Interesting Signals
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is too long for me to review in full detail. TBH I donβt fully understand all of the logic, but it seems this is still inactive after this PR, so I donβt think we should delay it further. Hopefully the other colleagues can review the remaining parts.
services/dynamic-scheduler/src/simcore_service_dynamic_scheduler/api/rest/_ops.py
Show resolved
Hide resolved
β¦-dy-scheduler-part2
|



What do these changes do?
Please π do not panic! There is a lot of code but the core of it composed of 1000 lines, where most of the attention is required.
Suggested review order: focus your review starting from
services/dynamic-scheduler/src/simcore_service_dynamic_scheduler/services/generic_scheduler/in the following order:_api.pyto have an idea of the methods the scheduler exposes_core.pyand look directly at_on_schedule_evenwhich introduces the logic behind the scheduler worksOperationlook at_operation.py, it might make more sense to read it form the bottom to the topThere is test coverage for all modules, for some it's pretty extensive.
This is the first of two PRs, The second one will bring a much required interface for monitoring the status of the scheduler.
The
generic_schedulermodule is the core of thedynamic-schedulerservice and was built to take into consideration some important requirements:During the last years it became apparent that we needed more flexibility during the starting and and closing of services. The idea here is to have a robust system that runs as much as possible without human intervention that can be easily debugged in case of issues.
Related issue/s
How to test
Dev-ops