In a hackathon we implemented a first prototype that allows to execute mappings created by the dynamic mapper.
Also we managed to use configuration management of C8Y to send mappings from the cloud to thin-edge devices which locally executed the mappings on the local mqtt broker.
As a next step we might need to improve the thin-edge.io mapping extension to also reports status back to C8Y about mapping stats (errors, executions etc.) but also the lifecycle of each mapping (Deployed, Undeployed, Enabled, Disabled)
When this information is available we could adapt the Dynamic Mapper UI to look for all thin-edge device in a tenant and display available & deployed mappings incl. the stats mentioned above. Also we should provide easy management by providing a deploy/Enable button.
Version management is another topic because now we need to detect if a mapping is changed and in sync with the one on thin-edge or cloud.
In a hackathon we implemented a first prototype that allows to execute mappings created by the dynamic mapper. Also we managed to use configuration management of C8Y to send mappings from the cloud to thin-edge devices which locally executed the mappings on the local mqtt broker.
https://github.com/albinsuresh/thin-edge.io/pull/new/dynamic-mapper
As a next step we might need to improve the thin-edge.io mapping extension to also reports status back to C8Y about mapping stats (errors, executions etc.) but also the lifecycle of each mapping (Deployed, Undeployed, Enabled, Disabled)
When this information is available we could adapt the Dynamic Mapper UI to look for all thin-edge device in a tenant and display available & deployed mappings incl. the stats mentioned above. Also we should provide easy management by providing a deploy/Enable button.
Version management is another topic because now we need to detect if a mapping is changed and in sync with the one on thin-edge or cloud.