1. IoT-devices need to get deployment solutions/manifests/other (TODO Use consistent name?)

[trkks]

Author  'juaatark'
Created 2023-01-11T16:42:34.784+02:00
Updated 2023-03-14T11:57:46.438+02:00

From the idea-paper's section 3.2:

Deployment manifests are sent to the devices, which then pull the necessary packages from the package repository. This process is depicted in block 3 of Fig. 1.

Said "packages" are (as far as I understand) the different .wasm files.

Needed:

• [x] Deployment file format (JSON, ~YAML, other?~)
• [x] Package identification (per deployment ~-> orch reads the matching manifest?~)
• ~[ ] Packaging (already started, maybe create separate issue)~

[trkks]

Author 'juaatark'
Originally created at 2023-02-14T17:08:03.800+02:00

For handling the WoT-format (if so chosen) this library might be nicer than just writing / validating JSON (Note: not sure if it does any validation on input).

[trkks]

Author 'juaatark'
Originally created at 2023-02-22T21:26:56.405+02:00

The deployment manifest sent to devices could probably be coupled with a WoT Thing Description of the module-set ('device' becomes a 'service' once it receives Wasm modules)?

[trkks]

[Sub discussion]
Author 'juaatark'
Originally created at 2023-03-01T17:12:33.326+02:00

After the weekly checkup, a way for the orchestrator to "push" deployments onto hardcoded devices was discussed. A POST endpoint on supervisor is needed for this, which I could probably hastly add. The actual description of the deployment would be an ordered (i.e., the sequence of operations?) list of modules (and the functions in them to call?).

[trkks]

[Sub discussion]
Author 'juaatark'
Originally created at 2023-03-10T13:30:12.975+02:00

Some attempts at 3f99e0169a45e876f814a571cb5d6b8cf52ecbaf. Not tested etc. but might help in realizing what info is needed and where.

[trkks]

Closing as packaging is a separate issue: https://github.com/LiquidAI-project/wasmiot-orchestrator/issues/4