tagged v2.0-beta5, the depsgraph release
Details
- Tag
- v2.0-beta5
tagged v2.0-beta5, the depsgraph release
This is the Flamenco Manager implementation in Go.
Flamenco Manager accepts the following CLI arguments:
$FM denotes the directory containing a checkout of Flamenco Manager, that is, the absolute path of this flamenco-manager-go directory.
0. Make sure you have MongoDB up and running (on localhost)
To run all unit tests, run go test ./flamenco -v. To run a specific GoCheck test, run go test ./flamenco -v --run TestWithGocheck -check.f SchedulerTestSuite.TestVariableReplacement where the argument to --run determines which suite to run, and -check.f determines the exact test function of that suite. Once all tests have been moved over to use GoCheck, the --run parameter will probably not be needed any more.
Flamenco Manager is responsible for initiating all communication between Server and Manager, since Manager should be able to run behind some firewall/router, without being reachable by Server.
In the text below, some_fields refer to configuration file settings.
0. Pushes happen as POST to "/api/flamenco/managers/{manager-id}/task-update-batch"
When a worker starts working on a task, that task moves to status "active". The worker then regularly calls /may-i-run/{task-id} to verify that it is still allowed to run that task. If this end-point is not called within active_task_timeout_interval_seconds seconds, it will go to status "failed". The default for this setting is 60 seconds, which is likely to be too short, so please configure it for your environment.
This timeout check will start running 5 minutes after the Manager has started up. This allows workers to let it know they are still alive, in case the manager was unreachable for longer than the timeout period. For now this startup delay is hard-coded.
In no particular order: