| [edge-wg] Eclipse Edge Native WG call minutes — September 2, 2020 |
Edge Landscape White paper
Robert Andres, Luca Cominardi and Frédéric Desbiens joined the August 31 white paper work session. Using the diagram put together by Luca as a starting point, they produced another diagram to position the working group in relation to various standard bodies, Foundations, and OSS Communities: https://docs.google.com/drawings/d/1JBxZF7REskHmw0oQQdCA_Tqswy1aXCmxzTWS1pqSyg4
They also took a first pass at positioning various Eclipse and non-Eclipse project on the cloud to edge continuum: https://docs.google.com/drawings/d/1bB04r512aqz1BwXR1oiIUSQAPmWEob6lOTyI481WKwA
Work will continue at a work session on September 9 @ 11am Eastern time. All are welcome to join.
People interested in the white paper should also join this channel in the Edge Native WG Slack.
Continue discussion on usage of Eclipse Ditto
There have been discussions in previous meetings about the role that various Eclipse IoT projects could play in an Edge Computing architecture. The aim is to determine how they could contribute to the implementation of universal hardware management capabilities. Eclipse Hono has been the focus of most conversations in the past since some of its team members regularly participated in the Edge Native WG’s community calls. Our community wished to know where Ditto could fit.
Thomas Jäckle made a technical presentation on Eclipse Ditto. This started a discussion on what Ditto brings to the table compared to Hono alone.
The ensuing exchange made clear that, in an IoT Edge architecture, granular authorization cannot be handled by Hono. Hono authenticates devices but does not care about the intent of the messages it routes. Ditto has sophisticated features to handle authorization.
At this point, it seems Ditto brings a lot of additional value.
Progress Check on Hono - ioFog integration
Kai Hudalla tried to integrate Hono and ioFog by connecting the ioFog agent to the Hono HTTP adapter. This attempt at a simple integration failed. The ioFog Controller exposes a REST API that Hono does not provide, obviously. Hono’s adapters expose endpoints where clients publish telemetry or events. They can be used to send commands to devices and wait for responses using generic messages but the ioFog agent does not support this in its current state.
The proper way to go forward is probably to rewrite the ioFog agent to make it support different modes of interaction and make it more portable. For the time being, it is tightly coupled to Linux and there is demand to have it support Windows, for example.
Frédéric DESBIENS
Program Manager, IoT and Edge Computing | Eclipse Foundation, Inc.
Twitter: @BlueberryCoder
Join us at our virtual event: EclipseCon 2020 - October 20-22