Detail the specification and architecture for job orchestration
Estimated focus duration (perfect conditions): 4 days
Estimated pessimistic duration (worst case scenario): 6 days
Who
- @kabir.kbr -- architect
- @0xPravar @joao.castro5 @dagimsisay @janaina.senna -- reviewers
What
- Detail the sequence diagram for job orchestration to improve understanding.
How
- Detail the
dms.orchestrator.getComputerProviderList()in Push-based search and match - Define a local data structure for storing peer information, including capacity, availability, price, etc.
- Specify an interface for a background task responsible for updating the above local structure, taking into account the utilization of different protocols/frameworks such as DHT and gossip protocol.
Why
- Detailing out sequence diagram will aid design discussions
- It will eventually lead to formulation of specification as per our documentation process
When
- No dependencies
Acceptance Criteria
Click to expand
Work Breakdown Structure (WBS)
| Task | Description | Duration | Status | Start Date | End Date | Comment |
|---|---|---|---|---|---|---|
| A-1 | Review status of related packages specifications (jobs, network, executor, etc) and mostly initial job orchestration | 3h | Done | 2024-04-21 | 2024-04-22 | see comment1874600533 below |
| A | Specify allocations as actors (send and receive messages via standard routing mechanisms) | 5h | Partially done | 2024-04-22 | 2024-04-22 | specified as much as it makes sense at this point and moving to the next task. see comment1875808182 |
| B | Identification and CID / routing (a.k.a. DHT vs gossip) | 4h | Partially done | 2024-04-30 | 2024-04-30 | see comment1888236476; remaining part is to figure the use of proposed channel interface... |
| C | JobManager specification | 3h | Partially done | ref: Orchestration, job, and executor designs | ||
| D | Pull orchestration (finding best machine for deployment) | 12h | Done | 2024-05-01 | 2024-05-06 | Based on results of all above tasks, most importantly A-1; see comment1888617539 and 1894913931 |
| E | Review and update all related packages, including database, background_tasks, network, etc. | 2h | Partially done | 2024-05-07 | 2024-05-07 | Some cosmetic changes have beed node to orchestrator/README.md, but the whole task postponed after the all existing proposed designed is merged |
| F | Consider implications for NuNet Solutions specifications, most importantly, Kubernetes integration | 1h | Not to be done in this iteration | ref: Kubernetes integration specs blog and further specifications | ||
| Total | 32h |
Edited by kabir