mirror of
https://github.com/kemko/nomad.git
synced 2026-01-01 16:05:42 +03:00
4415fabe7d
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 16" # partial cron, with only {minute} {hour}
timezone = "EST" # anything in your tzdb
}
}
...
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.
22 lines
452 B
Go
22 lines
452 B
Go
// Copyright (c) HashiCorp, Inc.
|
|
// SPDX-License-Identifier: BUSL-1.1
|
|
|
|
//go:build !ent
|
|
// +build !ent
|
|
|
|
package allocrunner
|
|
|
|
import (
|
|
"fmt"
|
|
|
|
"github.com/hashicorp/nomad/nomad/structs"
|
|
)
|
|
|
|
func (ar *allocRunner) SetTaskPauseState(string, structs.TaskScheduleState) error {
|
|
return fmt.Errorf("Enterprise only")
|
|
}
|
|
|
|
func (ar *allocRunner) GetTaskPauseState(taskName string) (structs.TaskScheduleState, error) {
|
|
return "", fmt.Errorf("Enterprise only")
|
|
}
|