jobspec: time based task execution #22201
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
this is the CE side of an Enterprise-only feature.
a job trying to use this in CE will fail to validate.
to enable daily-scheduled execution entirely client-side,
a job may now contain:
task "name" {
schedule {
cron {
start = "0 12 * * * *" # may not include "," or "/"
end = "0 4" # partial cron, with only {minute} {hour}
timezone = "EST" # anything in your tzdata
}
}
...
and everything about the allocation will be scheduled as usual,
but if outside the schedule, the taskrunner will block,
waiting on the schedule start, before proceeding with the task
driver execution, etc.
this includes a taksrunner hook, which watches for the end
of the schedule, at which point it will kill the task.
then, restarts-allowing, a new task will start and again block
waiting for start, and so on.
this also includes all the plumbing required to pipe API calls
through from command->api->agent->server->client, so that tasks
can be force-run, force-paused, or resume the schedule on demand.
Co-Authored-By: Michael Schurter <[email protected]>
Co-Authored-By: Seth Hoenig <[email protected]>
gulducat
force-pushed
the
f-time-based-task-execution
branch
from
c6346c7 to
8cc336e
Compare
schmichael
approved these changes
May 22, 2024
| helpText := ` | ||
| Usage: nomad alloc pause [options] <allocation> <task> | ||
|
|
||
| Set the pause state of an allocation. This command is used to suspend the |
There was a problem hiding this comment.
Note to myself that we should make sure this help matches the docs (once I write them!)
|
Don't forget a changelog entry |
Co-authored-by: Michael Schurter <[email protected]>
* Fragment and init * 4-state 2-button alert box * Small cleanup
Ember Test Audit comparison
|
|
I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
this is the CE side of an Enterprise-only feature. a job trying to use this in CE will fail to validate.
to enable daily-scheduled execution entirely client-side, a job may now contain:
and everything about the allocation will be placed as usual, but if outside the specified schedule, the taskrunner will block on the client, waiting on the schedule start, before proceeding with the task driver execution, etc.
this includes a taksrunner hook, which watches for the end of the schedule, at which point it will kill the task.
then, restarts-allowing, a new task will start and again block waiting for start, and so on.
this also includes all the plumbing required to pipe API calls through from command->api->agent->server->client, so that tasks can be force-run, force-paused, or resume the schedule on demand.