Action Tracker - Technical

Action Tracker - Technical

Description and Owner

Due Date

Status

Description and Owner

Due Date

Status

1
@michael.stuber Create an action tracker

2025/2/3

Complete

2
@eloi.bail @Rick Steurer Examine options for light-weight containerization (e.g. microcontainers, rootless containers, etc.) and present them to the technical team, being sure to address concerns regarding size and overhead.

2025/3/4

Materials presented at 2025/3/4 meeting. Posted at https://lf-energy.atlassian.net/wiki/spaces/GEISA/pages/228130830

3
@eloi.bail Examine container engine options (e.g. LXC, LXD, Moby, Balena, etc.)

2025/3/4

Being worked with item #2

4
@michael.stuber Explore options for application management

2025/4/1

In process. Updates are posted on Confluence. Brandon Thayer to join effort.

Team met week of 2/25 to discuss. Planning on presenting findings at 1st Technical meeting in April.

5
@Jeorge Olague Present on application management solution Welotec anticipates open-sourcing

2025/3/18

Technical presentation on March 18.

Complete

6
Create a proposal for device classifications for discussion. @richard.lam @Rick Steurer

Progress update 2025/2/18

Started. Rick, Michael, Brandon, and Richard met to discuss how devices should be characterized. The sub-team recommends individual attributes, rather than classifications. Decision made to use attributes. Richard to schedule sub-team meeting.

7

Work on a minimum viable product

@richard.lam

Working session proposed for 2025/4/4 @ 9 am PDT to discuss.

Richard has been working on the release roadmap on confluence. Committee members are encouraged to review the page.

8

2025/3/28

 

9
@matt.casperson to look at the variances between the following to better understand if there are material differences/considerations:
system d containerization vs. lxc containerization
zeromq vs. dbus

2025/5/6

See:

LxD & SystemD Security Considerations

https://lf-energy.atlassian.net/wiki/x/SgBIEQ

10
Norm Mcentire & @Brandon Thayer to research ZeroMQ & DBUS as potential message bus options. Report back for discussion and decision during 2025/5/6 meeting

2025/5/6

 

11
@Brandon Thayer to research systemd permissions;
@Bryan Green to research lxc permissions

Goal: To propose a set of reasonable high-level GEISA permissions which can be mapped to different containerization engines

2025/5/20

Bryan – work is in progress. To discuss June 17th. Brandon has posted materials on Github.

12
Matt Gillmore and Will Bell to propose which LWM2M objects make the most sense to use for GEISA, and where we need to extend them

2025/5/6

Presented 2025/5/20

13
@Brandon Thayer & @Rick Steurer (potentially with assistance from Norm Mcentire to provide a side-by-side comparison between ZeroMQ and RabbitMQ

Selection Criteria:

  • Library Size

  • Availability of Implementations (Multiple sources; Open Source; Commercial)

  • Ease of Implementation

  • Human Readable

  • Consistency / Limiting the number of technologies

2025/5/6

 

14
Craig to provide a proposed waveform frame definition for further review

 

 

15
Craig, Will Bell, and Vlad Pambucol to provide a proposal on normalized measurement values to be exposed via the message bus API

 

Materials provided via email on 2025/5/14. See https://lists.lfenergy.org/g/geisa-discussion/message/31

16
Vlad Pambucol to provide a standardized list of events that the execution environment should be to inform applications about

 

https://lf-energy.atlassian.net/wiki/spaces/GEISA/pages/290717727

https://lf-energy.atlassian.net/wiki/spaces/GEISA/pages/290717714

17
@Michael Garrison Stuber Document container “format” proposal

2025/5/23

 

18
Research on Message format (e.g. Protobuf, MessagePak, etc.) @Rick Steurer

2025/5/20

To discuss at face-to-face

19
@Michael Garrison Stuber Document format formal specification

2025/5/20

https://lf-energy.atlassian.net/wiki/spaces/GEISA/pages/361955341

20
@Will Bell to coordinate a meeting on API Transactions for Instantaneous Data & Billing Data with @Vlad Pambucol , @Craig Cornwall & @Balagopal Mathoor and provide updated transactions

2025/8/5

Team met multiple times. One MQTT topic for billing. One topic for instantaneous. There will be a meta-data source for things like data push frequency. Potentially add to platform enumeration.

21
@David Johnson to coordinate a meeting on API transactions for Platform Status, Platform Enumeration, and Networking with @Bryan Green and provide updated transactions

2025/8/5

David & Bryan met. Materials submitted. More to come. More by 2025/9/16

22
@Will Bell to coordinate a meeting on ADM transactions for Firmware & Software Updates with @Michael Garrison Stuber & Matt Gilmore and provide usage guidelines

2025/8/5

New draft published at https://lf-energy.atlassian.net/wiki/spaces/GEISA/pages/380141570

23
@Michael Garrison Stuber to update reorganize specification and update ADM section

2025/9/2

Initial Reorg Complete.

24
@Craig Cornwall Propose base libraries that should be present in a VEE.

2025/8/5

Making progress. Not quite ready yet. Pushed to 2025/9/16

25
@richard.lam Write up an explanation about baseline versus optional with respect to instantaneous values.

2025/9/19

In progress.

Backlog Table

#

Description

Priority

Status

#

Description

Priority

Status

 

https://lf-energy.atlassian.net/wiki/spaces/GEISA/pages/215482424 diagram needed. System Design Drawing similar to Margo needed:
https://specification.margo.org/margo-overview/introduction-system-design/

GEISA 1.0

 

 

https://lf-energy.atlassian.net/wiki/spaces/GEISA/pages/125239339 - Need to incorporate aspects from 10-15-2024 Technical Call regarding additional research.

GEISA 1.0

 

 

https://lf-energy.atlassian.net/wiki/spaces/GEISA/pages/125304872

https://lf-energy.atlassian.net/wiki/x/BoBPB

GEISA 1.x or 2.0