MobiQuitous 2020 - 17th EAI International Conference on Mobile and Ubiquitous Systems: Computing, Networking and Services 2020
DOI: 10.1145/3448891.3448938
|View full text |Cite
|
Sign up to set email alerts
|

Visually-defined Real-Time Orchestration of IoT Systems

Abstract: In this work, we propose a method for extending Node-RED to allow the automatic decomposition and partitioning of the system towards higher decentralization. We provide a custom firmware for constrained devices to expose their resources, as well as new nodes and modifications in the Node-RED engine that allow automatic orchestration of tasks. The firmware is responsible for low-level management of health and capabilities, as well as executing Mi-croPython scripts on demand. Node-RED then takes advantage of thi… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
4
0

Year Published

2021
2021
2024
2024

Publication Types

Select...
5
2

Relationship

2
5

Authors

Journals

citations
Cited by 7 publications
(4 citation statements)
references
References 29 publications
0
4
0
Order By: Relevance
“…As future improvements to the instrumented MQTT broker, we consider the following: (1) simplify the fault-injection configuration by supporting more native language constructs (e.g., arrow functions) and other configuration abstractions (e.g., leverage visual notations), (2) support wildcard topics as per the MQTT specification, and (3) enable switching configuration at run-time instead of having to specify the configuration file when starting the broker. Regarding the experimental stage, it would be interesting to (1) expand the scenarios with more experiments, including more extensive fault-injection pipelines; (2) replicated the experiments using different datasets; (3) extend the usage of self-healing mechanisms, especially the ones implemented as part of SHEN [16]; and (4) explore decentralized systems and orchestrators [34,39].…”
Section: Discussionmentioning
confidence: 99%
“…As future improvements to the instrumented MQTT broker, we consider the following: (1) simplify the fault-injection configuration by supporting more native language constructs (e.g., arrow functions) and other configuration abstractions (e.g., leverage visual notations), (2) support wildcard topics as per the MQTT specification, and (3) enable switching configuration at run-time instead of having to specify the configuration file when starting the broker. Regarding the experimental stage, it would be interesting to (1) expand the scenarios with more experiments, including more extensive fault-injection pipelines; (2) replicated the experiments using different datasets; (3) extend the usage of self-healing mechanisms, especially the ones implemented as part of SHEN [16]; and (4) explore decentralized systems and orchestrators [34,39].…”
Section: Discussionmentioning
confidence: 99%
“…We have also identified some limitations, which might be presented as future work, including: (1) resilience to network partitions, as the Redundancy node has no way of finding if there is already a master in the network; (2) most of the nodes still do not support the definition of reasonable margins (e.g., in nodes that deal with timing constrains, a minor delay should be ignored instead of triggering the recover or maintenance action); (3) although its need was identified, no mechanism to synchronize the current system state between different Node-RED instances has been provided, and (4) the capabilities of the DEVICE REGISTRY pattern and device/service discovery are only partial due to the high heterogeneity and lack of standard of IoT systems. Further, current state-of-the-art do not present out-of-the-box solutions for distribution of computational tasks across devices in the heterogeneous IoT system beyond limited (both in scope or supported devices) proofs-of-concept [31], [40], [32], [33], [34], [35], solutions which, if available, would offer foundations for other kinds of fault-tolerance mechanisms beyond the ones presented. Additionally, to be able to validate the correct functioning of our approach, there is the need of a solution that allows one to deliberately provoke failures in the system and report observed behaviours -in cloud computing defined as chaos engineering or fault injection.…”
Section: Discussionmentioning
confidence: 99%
“…There was also some literature found on the evolution of Node-RED with fault-tolerance considerations. The work by Margarida et al [31] propose a modification to Node-RED that allows the automatic decomposition and partitioning of the system towards higher decentralization, by running a custom firmware on the IoT devices. The system reliability is increase since Node-RED nodes could be automatically assign nodes to devices based on pre-specified properties and priorities, thus when abnormal run-time conditions were observed, the system reconfigured itself (i.e., self-configuration and self-healing).…”
Section: Related Workmentioning
confidence: 99%
“…Several extensions have been made, such as [210] tackling the reusability issues in cloud-based modeled components, [211] to tackle the heterogeneity and complexity challenges found in the Fog based development. Finally, in [212], the authors presented SHEN to enable self-healing capabilities of applications based on Node-RED.…”
Section: Tools and Platformsmentioning
confidence: 99%