Flamenco/debug-job-echo.sh

#!/bin/bash

curl -X 'POST' \
  'http://localhost:8080/api/v3/jobs' \
  -H 'accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
  "metadata": {
    "project": "Debugging Flamenco",
    "user.name": "dr. Sybren",
    "duration": "long"
  },
  "name": "Talk & Sleep longer",
  "priority": 3,
  "settings": {
    "sleep_duration_seconds": 20,
    "sleep_repeats": 1,
    "message": "Blender is {blender}"
  },
  "type": "echo-sleep-test",
  "submitter_platform": "manager"
}'
Little debug script for creating simple test job 2022-02-21 18:47:44 +00:00			`#!/bin/bash`

			`curl -X 'POST' \`
Update job submission URL in debug shell scripts Add `/v3/` component introduced in 9daecf2b 2022-07-05 09:53:37 +00:00			`'http://localhost:8080/api/v3/jobs' \`
Little debug script for creating simple test job 2022-02-21 18:47:44 +00:00			`-H 'accept: application/json' \`
			`-H 'Content-Type: application/json' \`
			`-d '{`
			`"metadata": {`
Debugging: add simple render job script 2022-02-21 18:58:29 +00:00			`"project": "Debugging Flamenco",`
Implement may-I-keep-running protocol Worker and Manager implementation of the "may-I-kee-running" protocol. While running tasks, the Worker will ask the Manager periodically whether it's still allowed to keep running that task. This allows the Manager to abort commands on Workers when: - the Worker should go to another state (typically 'asleep' or 'shutdown'), - the task changed status from 'active' to something non-runnable (typically 'canceled' when the job as a whole is canceled). - the task has been assigned to a different Worker. This can happen when a Worker loses its connection to its Manager, resulting in a task timeout (not yet implemented) after which the task can be assigned to another Worker. If then the connectivity is restored, the first Worker should abort (last-assigned Worker wins). 2022-05-12 09:04:05 +00:00			`"user.name": "dr. Sybren",`
			`"duration": "long"`
Little debug script for creating simple test job 2022-02-21 18:47:44 +00:00			`},`
Implement may-I-keep-running protocol Worker and Manager implementation of the "may-I-kee-running" protocol. While running tasks, the Worker will ask the Manager periodically whether it's still allowed to keep running that task. This allows the Manager to abort commands on Workers when: - the Worker should go to another state (typically 'asleep' or 'shutdown'), - the task changed status from 'active' to something non-runnable (typically 'canceled' when the job as a whole is canceled). - the task has been assigned to a different Worker. This can happen when a Worker loses its connection to its Manager, resulting in a task timeout (not yet implemented) after which the task can be assigned to another Worker. If then the connectivity is restored, the first Worker should abort (last-assigned Worker wins). 2022-05-12 09:04:05 +00:00			`"name": "Talk & Sleep longer",`
			`"priority": 3,`
Little debug script for creating simple test job 2022-02-21 18:47:44 +00:00			`"settings": {`
Implement may-I-keep-running protocol Worker and Manager implementation of the "may-I-kee-running" protocol. While running tasks, the Worker will ask the Manager periodically whether it's still allowed to keep running that task. This allows the Manager to abort commands on Workers when: - the Worker should go to another state (typically 'asleep' or 'shutdown'), - the task changed status from 'active' to something non-runnable (typically 'canceled' when the job as a whole is canceled). - the task has been assigned to a different Worker. This can happen when a Worker loses its connection to its Manager, resulting in a task timeout (not yet implemented) after which the task can be assigned to another Worker. If then the connectivity is restored, the first Worker should abort (last-assigned Worker wins). 2022-05-12 09:04:05 +00:00			`"sleep_duration_seconds": 20,`
Add `sleep_repeats: 1` to `debug-job-echo.sh` Add a `sleep_repeats: 1` setting to `debug-job-echo.sh`. It doesn't change the behaviour of the job, but it does make it visible that this setting exists, and that it can be used to generate a large number of tasks. 2022-07-07 08:26:18 +00:00			`"sleep_repeats": 1,`
Implement may-I-keep-running protocol Worker and Manager implementation of the "may-I-kee-running" protocol. While running tasks, the Worker will ask the Manager periodically whether it's still allowed to keep running that task. This allows the Manager to abort commands on Workers when: - the Worker should go to another state (typically 'asleep' or 'shutdown'), - the task changed status from 'active' to something non-runnable (typically 'canceled' when the job as a whole is canceled). - the task has been assigned to a different Worker. This can happen when a Worker loses its connection to its Manager, resulting in a task timeout (not yet implemented) after which the task can be assigned to another Worker. If then the connectivity is restored, the first Worker should abort (last-assigned Worker wins). 2022-05-12 09:04:05 +00:00			`"message": "Blender is {blender}"`
Little debug script for creating simple test job 2022-02-21 18:47:44 +00:00			`},`
Fix T99434: Two-way Variables Two-way variable implementation in the job submission end-point. Where Flamenco v2 did the variable replacement in the add-on, this has now been moved to the Manager itself. The only thing the add-on needs to pass is its platform, so that the right values can be recognised. This also implements two-way replacement when tasks are handed out, such that the `{jobs}` value gets replaced to a value suitable for the Worker's platform as well. 2022-07-21 14:41:40 +00:00			`"type": "echo-sleep-test",`
			`"submitter_platform": "manager"`
Little debug script for creating simple test job 2022-02-21 18:47:44 +00:00			`}'`