29 lines
955 B
Markdown
29 lines
955 B
Markdown
# Tentacles
|
|
|
|
A simple queue system for OctoPrint, designed to receive jobs and forward them to connected OctoPrint instances as they are available and ready.
|
|
|
|
## Workflow
|
|
|
|
Username+Password users
|
|
|
|
API keys mapped to users (same thing as sessions actually)
|
|
|
|
Users mapped to job priority
|
|
|
|
API keys mapped to user sub-priority
|
|
|
|
User-facing API can upload gcode files to storage and create a file entry in the DB
|
|
|
|
Jobs can be created from new or existing file entries in the DB
|
|
|
|
Jobs are mapped to the priority of the API key (and user) who created them
|
|
|
|
Jobs get Runs - which track assigning a pending Job to a Printer
|
|
|
|
Highest priority job schedules first/next non-Running Job to the first available printer.
|
|
This requires copying the gcode file to the target device, and starting it running.
|
|
|
|
Running Runs are polled to detect loss/failure. Lost or failed Runs are deleted, and the Job returns to the queue.
|
|
A priority penalty may be called for.
|
|
|
|
## Notes
|