4. Actor needs way to request desired functionality

LiquidAI-project / wasmiot-orchestrator

MIT License

0 stars 1 forks source link

4. Actor needs way to request desired functionality #6

Closed trkks closed 1 year ago

trkks commented 1 year ago

Author  'juaatark'
Created 2023-01-11T17:13:01.029+02:00
Updated 2023-03-07T11:54:38.945+02:00

In idea-paper section 3.2:

The Orchestrator looks for suitable deployment solutions for such functionality by comparing available packages, and devices with suitable capabilities on its devices database. Upon finding a solution, a new service namespace is created for a service, which contains a suitable list of devices, their connections and needed packages.

Needed:

[x] Stored information about devices #5 and packages #7
[x] Service namespace containing information in quote above

trkks commented 1 year ago

Author 'juaatark'
Originally created at 2023-01-24T15:23:58.951+02:00

Make some crummy user interface for this? "Node editor" relevant here?

trkks commented 1 year ago

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

For start just a form to submit JSON onto the server

trkks commented 1 year ago

Author 'juaatark'
Originally created at 2023-03-01T17:03:22.908+02:00

Added a simple form where JSON can be copy-pasted onto a textarea 0416d5378c07ed751078af274aff246926db12d0

trkks commented 1 year ago

For the 2nd bullet:

On deployment solution creation it can be seen here that:

[x] The "service namespace" created is the deployment's ID
[x] To this namespace:
- [x] needed modules
- [x] and connections (= instructions and sequence)
- [x] are mapped to each device (in fullManifest)

As per the observations above I'm closing this as completed.