jobs package design

Key Points

1. Manage jobs locally on DMS through whatever executor it's running (container, vm, direct_exe, java etc...) -- design;
2. A more general job management package that utilizes the executors. Will be used by the orchestrator package to deploy jobs.
3. The general goal with this package is to have a module that’s able to run jobs. No matter what type of process it is or what executor it needs to use, the jobs package will be responsible for starting it, tracking its health and reporting to the Orchestrator, collecting the logs the process produces and managing its lifecycle such as starting, pausing, resuming and killing it. The Jobs package will essentially serve as a coupler between the orchestrator and the executor

Work Package Deliverables

No	Deliverable	Proof
1	Design jobs package as per the job orchestration semantics (defined in research blog)	Designed and specified as per our specification process

Timeline

Additional notes and context

1. Related to the executor package implementation and design;
2. Related to the orchestrator package implementation and desigh;
3. Potentially related bacalhau packages to check in design and implementation pkg/job pkg/jobstore;