Mar 18, 2024 ‐ 16:00 UTC

Host:

• Philipp Ahmann

Participants:

First meeting

• Walt Miner
• Kate Stewart
• Alfred Strauch
• Steven Carbno

Second meeting

• Nicole Pappler
• Andreas Bartelt
• Thomas Mittelstädt
• Stewart Hildebrand

Regrets:

• ...

Attended Recently

• Guy Lunardi
• Olivier Charrier

Topics & Notes:

Check past action items

• Last meeting minutes: https://github.com/elisa-tech/wg-systems/wiki/Mar-11,-2024-%E2%80%90-16:00-UTC
• AI-Philipp-Thomas: Need to schedule a follow-up with ZAL (Aerospace research centre in Hamburg, Germany)
  • Follow up call on Wednesday morning European time.
  • ZAL considers domain separation on single HW platform.
• AI-Philipp-Nicole: Need to have also a follow-up on Nix & NixOS as they were interested in the SBOM topic.
  • Nix OS call happened today. Some information below.
  • Item closed. Topics to follow up during Lund WS and OSS EU.
• AI-Alfred-Philipp: Alfred may be able to present something about HBOM for the meeting April 8th.
  • Shift to April 22nd due to availability issues of participants

Report from Nix OS call and discussion

• Nix plans to submit CfP on reproducible Linux OS for OSS EU (safety-critical track)
• Nix considers to participate in Lund WS
• Nix seem to be far more complex and flexible than yocto is.
• Uses different approaches on how to treat packages and self contained environment.
• Nix OS is a mixture of Ansible, Yocto, Package Based Distro and Container technologies.
• Should put some new sparks and ideas to the way of creating a Linux system.
• Erin van der Veen is responsible for SBOM activities in Nix.
• https://nixos.org/

2nd meeting notes

• Philipp also had follow-up with AGL who raised some aspects to consider about Nix.
  • Complexity of tooling. Kind of own language to learn
  • More complex than yocto and more flexible.
  • You can decide which application uses which part of libraries (e.g. two different version of curl, openssh, wayland)
    • this is kind of container without container
  • Community is still smaller and growing and not yet so mature.
  • SBOM for Nix get quite complicated in case you mix library version for different system parts.
• How to avoid conflicts when libraries use same resources? It is not so easy.

Next steps to System SBOM

• Create a BOM directory in Systems WG repo
• Document how to create SBOM parts for system elements (Zephyr, Xen, Linux)
• Show the impact of qemu vs. physical hardware.
• Point to SPDX for Safety work.
• Can be entry point for later HBOM topics in ELISA (Link to Alfred's presentation April 22nd)
• Philipp can start looking into something first week of April. Needs more support from others as well.
• Start initial brainstorming (really just initial parts) in a gdoc before putting the result in GitHub repo.
  • DRAFT - ELISA SBOM Generation

AoB

• Alfred to talk about HBOM on April 22nd in Systems WG meeting.
• No meeting March 25th and April 1st due to host unavailability
• June Workshop registration open: https://lists.elisa.tech/g/devel/message/2182
• Proposal for Plumbers
  • Reach out also for TI people (as they were active last time)
  • Some discussion was also happening in TSC: https://github.com/elisa-tech/tsc/wiki/06-Mar-2024#plumbers-mini-conf
  • Topics:
    • How to capture requirements for the Linux kernel in a way that community is happy with it?
      • Code, parallel to code, who can maintain it (e.g. independent of maintainers but in same repo.)
      • Testing and traceability from feature to testing and have a link. How to bind it to code submission?
      • BASIL and it's effective usage. How to get wider sourcing and need to have it in sign-off.
      • Where is the place to get requirements work started.
      • Some work is already there, which would just need more formal language
    • Maybe we do not need 7-8 proposals, but more ~4 major topic areas
    • Plumbers micro-conf deadline is April 4th
  • Continue this during next TSC meeting