Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[edge-wg] Eclipse Edge Native WG call minutes — November 25, 2020

Hi everyone.

You will find the minutes from the November 25, 2020 call below. Minutes from prior meetings are also available in this document:
https://docs.google.com/document/d/1XIv3-SYK-HadgScJ_H4tKvwRhGsig7uLg7n0Xzvwza0  


Meeting recording
https://eclipse.zoom.us/rec/share/cG7leO4-WYZ6SiATgKhJNvwyE37L7aUS0VU0DM7FxuLisNbJ_Wk6Wh-fJJ-OAcuv.nq2lKmIzdreP-Qe4 Passcode: .6cPD6.O

The next call will be held on December 9, 2020.

=====
  1. Project updates

    1. zenoh 
      Luca Cominardi stated that the zenoh team recently added support for influxDB as a storage backend. Support for the local filesystem as a backend is in the works.

      Nightly builds for zenoh-pico, a client-only version of the protocol library aimed at very constrained devices, will be available starting next week (November 30, 2020). The next beta release for zenoh and zenoh-pico will be out before Christmas (Beta 6).


    1. fog05
      The fog05 Rust rewrite is still ongoing. The team is currently working on the networking layer. They are also implementing RPC over zenoh; this is a way to deliver an API that abstracts zenoh primitives and will be easier for developers to pick up. 

    2. ioFog
      ioFog agent 2.0.3, which has just been published, fixes some bugs discovered in the field. In particular, it addresses a nasty pruning issue where a node rebooting after reaching its disk threshold would prune every microservice image.

      The next release will be ioFog 2.1. New features will be initial support for Edge Resource modeling and ECN Viewer improvements.


  1. Edge Node Hardware metamodel

The text below is a summary of the discussion.


A big challenge to solve in order to expose the hardware capabilities of Edge nodes is to detect the devices available in proximity of the node. Detecting devices over USB is fairly simple, if the device makers did their homework at least. But what about devices using MODBUS over ethernet, for example? And devices connected to a serial port?

In the case of network connected devices, the network itself can be a stumbling block. Some protocols such as CoAP and DDS rely on multicast packets for device discovery. If the network layer blocks those, discovery is impossible. Real world deployments also involve multiple networks and protocols, making discovery even more difficult. For older devices using serial connections, things are even more difficult. MODBUS implementations can vary a lot. 


Given this, human intervention to document the devices available and write descriptors for them is a possible solution. Writing such descriptors will be error prone and time consuming unless powerful templating mechanisms are used, however. The Eclipse Vorto repository and DSL could be used to document the devices and generate YAML descriptors.




  1. WebAssembly primer (TBC)

Rex St. John could not attend the meeting; this point was thus dropped from the agenda.


=====

Best Regards,

Frédéric DESBIENS

Program Manager, IoT and Edge Computing | Eclipse Foundation, Inc.

Twitter: @BlueberryCoder

Eclipse Foundation: The Platform for Open Innovation and Collaboration


Back to the top