June 2023 - automotive-sig - lists.centos.org

[REPORT] Quarterly Report - CentOS Automotive SIG
by Jeffrey Osier-Mixon 17 Aug '23

17 Aug '23

January 2023 Quarterly report submitted by: Jefro Osier-Mixon, Red Hat - chair _____________________________________ Membership update This SIG does not have a formal membership process. The mailing list currently has 106 subscribers representing at least 32 organizations, though not all subscribers use corporate emails and some are participating as individuals. _____________________________________ Releases in the most recent quarter (or most recent release, if none in that quarter) The Automotive SIG produces three types of artifacts: - AutoSD, a streaming distribution of CentOS designed for in-vehicle automotive use cases. - An Automotive SIG RPM repository that allows the community to expand the content of AutoSD or experiment with some of its parts. - Sample images, built using OSBuild, which provide examples of how to assemble production images based on AutoSD, customized for some hardware, including container images, based on CoreOS/ostree technologies. AutoSD, or Automotive Stream Distribution, is a streaming distribution for automotive in-vehicle software development based on CentOS Stream. It is transparently the upstream project for Red Hat's eventual in-vehicle OS product. AutoSD has been downloaded and used by many organizations who have commented or asked for help, so we know it is getting some traction though of course we don't have exact metrics on usage. In Q4 2022, we released a version of AutoSD compatible with the emerging SOAFEE specification. SOAFEE (https://soafee.io) is an initiative driven by Arm for the purpose of developing a reference specification for Arm-based software-defined vehicles (SDVs) consisting of an operating system, container orchestration strategy, and application layer. In addition, we introduced a very lightweight container runtime based on podman and systemd that does not include Kubernetes, as the latter represented a significant performance hit on all relevant hardware. We presented at the Arm Developer Summit in November on these topics. In the coming quarter, we plan to tighten up documentation, begin a process for accepting and supporting hardware enablement contributions, and continue to develop AutoSD toward the SOAFEE specification while also contributing to that specification within the SOAFEE community. _____________________________________ Health report and general activity narrative The SIG typically has 1 public meeting per month with 25-40 attendees, with visible participation from 7-10 separate organizations. We have largely given up on a separate office hours meeting due to attendance. This SIG is intended to be a community effort with contributions and shared benefits from all participants. All formal meetings are recorded and posted on this page: https://wiki.centos.org/SpecialInterestGroup/Automotive/Meetings Several Red Hat employees made the initial contributions to the project as well as the infrastructure required to build and test it. We occupy a gitlab repository in the CentOS namespace building software regularly using CI, with build instructions provided on the documentation page at https://sigs.centos.org/automotive/ . Sample images are present and downloadable along with customization and build instructions. _____________________________________ Issues for the board to address, if any None, keep up the excellent work :) Jeffrey "Jefro" Osier-Mixon | jefro(a)redhat.com Red Hat Office of the CTO | Sr. Principal Community Architect, Automotive

1 1

Container images repository
by Leonardo Rossetti 27 Jun '23

27 Jun '23

Hello, We've created a Quay organisation for the SIG: https://quay.io/organization/centos-sig-automotive to store/host SIG container images. Would it be possible to create a repository to store container images files as well? That repository would host container files for several images, leveraging Quay's CI features as well. Regards, -- Leonardo Rossetti Principal Software Engineer, Red Hat <https://www.redhat.com> lrossett(a)redhat.com <https://www.redhat.com>

3 11

Automotive SIG meeting moved to July 12
by Jeffrey Osier-Mixon 24 Jun '23

24 Jun '23

Hi all - I have moved the next auto SIG meeting to July 12, as I expect many US folks to be out of office on July 5 due to the Independence Day holiday. The wiki has been updated. See you then Jeffrey "Jefro" Osier-Mixon | jefro(a)redhat.com Red Hat Office of the CTO | Sr. Principal Community Architect, Automotive

1 0

dist-git repo for qemu packaging
by Sandro Bonazzola 09 Jun '23

09 Jun '23

Good morning, within digital cockpit team we'd like to have a qemu dist-git like repo to be used for building patched qemu on https://copr.fedorainfracloud.org/coprs/g/centos-automotive-sig/dui/ . Is it possible to get a repository for it under https://gitlab.com/CentOS/automotive/rpms ? Thanks, -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING - Red Hat In-Vehicle Operating System Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

2 3

Future of the neptune image
by Pierre-Yves Chibon 05 Jun '23

05 Jun '23

Good Morning Everyone, When we started this SIG we looked at ways to demonstrate autosd and what it could look like in an automotive context. One application we quickly ran into was the neptune application developed by Qt as an example automotive application showing a dashboard, speedometer and a few other elements. This served us well originally, but truth be told, we have not really done anything with this image for a while. Today neptune no longer starts when building the image and this ends up looking weird: we have this demo image that is practically not maintained (because it doesn't seem to be useful to us anymore) and that people may try but will be disappointed with since it doesn't work. So the question becomes: what do we want to do with that sample image? If there is still interest in it, let's fix it and check it regularly to make sure it remains working (e.g.: when neptune needs a rebuild because a newer Qt landed). If that image has served us well and is no longer of interest to us. I would like to propose that we retire it and wish it a well and happy retirement (based on git rm). Looking forward to hear your thoughts on this topic, Pierre PS: I had sent this email on May 25th but it looks like it never reached the list :( so here we go again :)

2 1

2024

2023

2022

2021

automotive-sig June 2023