From 4a02a8bca4939fbb23a4a240ea0980bee89007c5 Mon Sep 17 00:00:00 2001 From: Lorenzo Venerandi Date: Mon, 19 Aug 2024 19:16:17 +0200 Subject: [PATCH] Create readme.md --- task-splitter/readme.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 task-splitter/readme.md diff --git a/task-splitter/readme.md b/task-splitter/readme.md new file mode 100644 index 0000000..59704ad --- /dev/null +++ b/task-splitter/readme.md @@ -0,0 +1,22 @@ +# Scope of project +Tha annotation must tell the splitter how to aggregate and where to send each task. + +## Possible implementation + +The code will be processed and splitted into possible modules. Inside the path /build will be created a directory for each module. Inside there will be the wasm compiled bytecode, a file scheduler.config that will list all the information that schedule could need to schedule the module. + + +## Targets +Possible devices that run the task: +- Cloud device, prossibly the same cloud that runs the scheduler +- Edge device +- IoT device, the only one that can run device specific tasks + +## Annotations + +List of possible annotations: + +- `@TaskGeneric` defines a generic task that can run everywere +- `@CloudSpecific` runs only on cloud +- `@EdgeSpecific` runs only on edge +- `@EndDeviceSpecific` runs only on end device, in particular the device can be specified with `@EndDeviceSpecific(device_name)`