Gator is a combination of a task runner and a logging system. Every job is managed by a wrapper layer that monitors its progress, resource usage, and captures the messages that it emits via STDOUT or STDERR. Execution is managed in a hierarchical structure, with jobs at the leaves reporting back to layers of parent processes.
NOTE This project is under development is not feature complete, nor has it been battle tested.
Gator has been developed using poetry
for package management:
$> python3 -m pip install poetry
$> poetry install
Tasks to perform are specified in a custom YAML syntax, arranged into two distinct object types:
!Job
that describes a single task to perform;!JobGroup
that describes a set of tasks to perform, also supporting layers of nested groups;!JobArray
similar to a!JobGroup
, but repeats the set of described tasks a specified number of times.
A simple specification may look like this:
!JobGroup
ident : top
jobs:
# Nested layer
- !JobGroup
ident : inner
jobs:
- !Job
ident : say_hi
command: echo
args : ["hi"]
# Arrayed job - waits for 'say_hi' to complete
- !JobArray
ident : counting
on_pass:
- say_hi
repeats: 4
jobs :
- !Job
ident : echo_count
command: echo
args : ["$GATOR_ARRAY_INDEX"]
# Directly attached to root - waits for 'counting' to complete
- !Job
ident : say_bye
on_pass:
- counting
command: echo
args : ["bye"]
To run a given job specification, use the Gator CLI:
$> python3 -m gator examples/job.yaml
[17:58:50] Starting Gator 🐊
[INFO ] Launching task: echo hey there you
[INFO ] Monitoring task
[INFO ] hey there you
[INFO ] Task completed with return code 0
[INFO ] Recorded 0 warnings and 0 errors
To setup the hub:
- Install postgress app and follow the instructions to initialise a new server with the following settings:
- Host: localhost
- Port: 5432
- User: postgres
- Database: postgres
- Password: dbpasswd123
* Different options can be used if supplied to the hub command manually.
- Install npm and install hub packages
$> cd gator-hub
$> npm install
To run the hub:
$> poe hub
# OR
$> poe hub_dev
Running the hub will output the hub url. This can be used in gator commands to register with the hub e.g.:
$> python3 -m gator examples/job.yaml --hub localhost:8080
- Get hub working
- Pass artefacts between jobs and form artefact based dependencies
- Arbitrary metrics gathering - replace warning and error counts with a generalised mechanism that supports aggregation while summarising min, max, mean, sum, and count of metrics recorded
- Random number seeding
- Hooks
- Tool based log parsers
- Custom runners - currently everything is shell, perhaps support other things?
- Non-environment variable based parameters