Nov 11, 2024 ‐ 16:00 UTC
Host:
- Philipp Ahmann
Participants:
- Sebastian Hetze
- Daniel Weingaertner
- Walt Miner
- Nicole Pappler
Regrets:
- Kate Stewart
Attended Recently
- Alfred Strauch
- Steven Carbno
- Gabriele Paoloni
- Karen Bennet
- Guy Lunardi
- Andreas Bartelt
- Thomas Mittelstädt
- Stewart Hildebrand
- Olivier Charrier
-
Previous meeting notes: https://github.com/elisa-tech/wg-systems/wiki/Nov-04,-2024-%E2%80%90-16:00-UTC
-
AI-Philipp: Draw a picture which shows the interaction of all the initiatives currently around (CRA, Eclipse Automotive Process SIG, ELISA)
-
First draft in prep:
-
-
AI-Philipp: Draw a picture illustrating the project proposal in a graphical way.
-
First draft in prep:
-
-
AI-Sebastian: Involvement of DIN can also be interesting. Sebastian will take a first contact.
- Meeting scheduled this week Wednesday. Updates in next week.
-
AI: Invite the epam people to tell a bit about their work and planned activities.
- Philipp had good first touch point with Bucci-san in Japan.
- Text brought from gdoc to github wiki md file: https://github.com/elisa-tech/wg-systems/wiki/Software-Quality-Good-Practices-in-Open-Source-%E2%80%90-Proposal
- Linux Foundation Europe follow up Nov 12th
- Discuss with Eclipse SDV Process SIG on Nov 18th (positive response by most people)
- Additional literature relevant to the proposal identified:
- Pictures from action items added to the PR:
- Need to prepare further material as preparation for the meetings.
- ELISA Systems WG builds could be executed on ARM servers as a Qemu image
-
Initial idea to work on (implementation view):
- Bring the existing ZCU102 example into a generic ARM64 qemu image running on ARM server.
- Replace peta-Linux by AGL.
- Add stack elements from SCORE (eclipse-safe-open-vehicle-core) to promote SDV use case
- Have a boot test for the generated image running on the server.
- Generate an SBOM (Software) for the system elements Xen, Zephyr and Linux (yocto)
- Store SBOM results in a database
- Create same artifacts based on new Pull Requests.
- Consider how to treat the Hardware and have a HBOM part in the system composition
- How to track which hardware was used on the server being a virtual machine on a physical server.
- Kate and Philipp will have a follow up with ARM end of this week.
- Initial idea to work on SPDX view to work on to create data:
- We need to define what a "System" actually means!
- A system is a representation of included elements that are defined in other SBOMs. A computer system is defined as the integration of hardware, software, peripheral devices, data, and networking components. Together they perform computing tasks and facilitate user interaction. A system captures operational information such as relationships between the network, data, connections, and potentially operating systems ultimately enabling the performance of a wide range of tasks from basic computing to complex data analysis. The system is used to group components to define functionality or services. The grouping of services and functions impacts the definition and operation of a computing environment.
- Starting point: How does the ARM system actually look like.
- Next: How can we enhance this with the proper artifacts and add the parts of the safety SBOM.
- Once SPDX 3.2 is on the radar also check what does a virtual prototyping as base for physical embedded hardware mean for a HBOM.
- Which kind of different BOM need to be considered to fulfill regulatory demands by e.g. US and EU.
- https://www.cisa.gov/sites/default/files/2023-04/sbom-types-document-508c.pdf includes additional BOMs (maybe to early to have this as SPDX material for the database PoC)
- We need to define what a "System" actually means!
- Next week will be special meeting: ELISA meets Eclipse SDV Automotive Process SIG!