[CLOSED] 5. Orchestrator needs software packages/modules to distribute

[trkks]

Author  'juaatark'
Created 2023-01-11T17:15:00.863+02:00
Updated 2023-03-13T18:32:29.140+02:00
Closed  2023-03-13T18:31:52.923+02:00

Maybe just "hardcoded" modules are fine to save onto the eventual server.

Should make some Wasm-binaries that all run on the selected Wasm-runtime and are suitable for composing a couple(?) different services.

• [x] Come up with some use cases / services
• [x] Implement parts of them and compile to Wasm
• [x] Place somewhere for the orchestrator to get them from

[trkks]

Author 'juaatark'
Originally created at 2023-02-22T11:44:09.022+02:00

Repository for modules and Wasm-compilation in https://gitlab.jyu.fi/wasmiot/wasm_modules

[trkks]

Author 'juaatark'
Originally created at 2023-03-01T14:29:54.417+02:00

The modules stored on Orchestrator should have some more associated metadata such as how they are used (inputs/outputs) and what using/running them requires from the underlying device/platform (peripherals, other modules?).

[trkks]

Author 'juaatark'
Originally created at 2023-03-06T15:32:40.850+02:00

Starting to work on simple form for submitting module and its metadata and the needed server routes.

[trkks]

Author 'juaatark'
Originally created at 2023-03-06T18:39:13.775+02:00

Modules can be uploaded from a HTML-form on 6dd0a944eb233c7a949f5617800159be242f2363. Next up would be to add relevant metadata-fields.

[trkks]

Author 'juaatark'
Originally created at 2023-03-13T18:31:52.595+02:00

Modules with their metadata can now be uploaded to the database for orchestrator to use (commit e29aba0ac3d8024782e4bf5f773a49079f432c83).

Closing this now as

1. a use case exists converting an image to black and white
2. the need for additional fields is IMO another issue and this one is too vague.