Action Tracker - Technical
- michael.stuber
- matt.casperson
- richard.lam
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 Light-Weight Container Investigation |
| 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 | April face-to-face planning survey https://docs.google.com/forms/d/e/1FAIpQLSc6r8RItJy7CF0_NBw7FmWjbpQGB_bjMZ2OhQ8aZk-WadEd9w/viewform?usp=sharing | 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/05/05 |
|
| 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 |
|
| 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 |
|
| 13 | @Brandon Thayer & @Rick Steurer (potentially with assistance from Norm Mcentire to provide a side-by-side comparison between ZeroMQ and RabbitMQ Selection Criteria:
| 2025/5/? |
|
| 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 |
|
|
| 16 | Vlad Pambucol to provide a standardized list of events that the execution environment should be to inform applications about |
|
|
Backlog Table
# | Description | Priority | Status |
|---|---|---|---|
| Envisioned System Architecture diagram needed. System Design Drawing similar to Margo needed: | GEISA 1.0 |
|
| Security - Need to incorporate aspects from 10-15-2024 Technical Call regarding additional research. | GEISA 1.0 |
|
| GEISA 1.x or 2.0 |
|