- automotive-sig - lists.centos.org

December meeting CANCELLED
by Jeffrey Osier-Mixon 05 Dec '22

05 Dec '22

Canceling our December meeting, as several folks have a conflict and it would be a challenge to reschedule this late in the year. We will send a technical update by email this week. IF you would like a personal meeting, please let me know and I can try to find time to sync. Thanks all & happy new year! Jeffrey "Jefro" Osier-Mixon | jefro(a)redhat.com Red Hat Office of the CTO | Sr. Principal Community Architect, Automotive

1 0

December 7 meeting
by Jeffrey Osier-Mixon 02 Dec '22

02 Dec '22

Hi all - Pierre-Yves and I, as well as much of the Red Hat automotive team, have a conflict at our regular meeting time on Weds next week. My inclination is to cancel this meeting and send a thorough December update by email, but I can reschedule if needed, or hold a less formal call on a different day. Please let me know if you have strong feelings either way . Jeffrey "Jefro" Osier-Mixon | jefro(a)redhat.com Red Hat Office of the CTO | Sr. Principal Community Architect, Automotive

1 0

CentOS Automotive SIG meeting: Weds Nov 2
by Jeffrey Osier-Mixon 28 Oct '22

28 Oct '22

Hi all, this is just a reminder of the upcoming CentOS Automotive SIG meeting on November 2 to discuss the Automotive Stream Distribution and related subjects. This is a preliminary agenda, please feel free to drop me a note if you'd like to add anything. - Technical Status - Container solution: podman + systemd - Arm DevSummit & SOAFEE - the ever-present discussion about hardware The meeting is at 7am PDT, 10am EDT, 1500UTC. Let me know if you would like to be added to the Google calendar invitation. Hope to see you there! Jeffrey "Jefro" Osier-Mixon | jefro(a)redhat.com Red Hat Office of the CTO | Sr. Principal Community Architect, Automotive

1 0

Reminder: CentOS Automotive SIG meeting tomorrow
by Jeffrey Osier-Mixon 04 Oct '22

04 Oct '22

Hi all - just a quick reminder of the CentOS Automotive SIG meeting, which is happening tomorrow October 5 at 1500UTC, which is 7am PDT, 10am EDT, 4pm CEST. If you are not on the calendar invite and would like to be, just drop me a note and I can add you. As always, meetings are noted here: https://wiki.centos.org/SpecialInterestGroup/Automotive/Meetings best, Jeffrey "Jefro" Osier-Mixon | jefro(a)redhat.com Red Hat Office of the CTO | Sr. Principal Community Architect, Automotive

1 0

container-native ostree
by Colin Walters 03 Oct '22

03 Oct '22

Hi, as CentOS Automotive uses ostree today, I just want to call your attention to https://fedoraproject.org/wiki/Changes/OstreeNativeContainer and see also https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… This functionality is in CentOS Stream 9 today too. I'm working on a followup Change for this, but I would definitely recommend considering using ostree-containers at least on the *build* side to manage publishing images, etc. You could create quay.io/centos/automotive:latest *today* and it's really useful to be able to just quickly `podman run` the OS image to inspect it etc. (The derivation aspect is of course big too, if only for testing)

1 0

[REPORT] Quarterly Report - CentOS Automotive SIG
by Jeffrey Osier-Mixon 30 Sep '22

30 Sep '22

October 2022 Quarterly report submitted by: Jefro Osier-Mixon, Red Hat - acting chair _____________________________________ Membership update This SIG does not have a formal membership process. The mailing list currently has 99 subscribers representing at least 31 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 SIG provides a new distribution: Automotive Stream Distribution (AutoSD), a CentOS Stream derivative designed specifically around the needs of an automotive OS, and 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. _____________________________________ Health report and general activity narrative The CentOS Automotive SIG celebrated its first year anniversary in August. The SIG has typically had 1-2 public meetings per month, one formal and one informal "office hours", each with 25-40 attendees, with visible participation from 7-10 separate organizations. The office hours portion has been on hiatus since July as summer vacations brought attendance to a crawl, but we intend to start them back up in October. 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. This is a high-level summary of activity over our first year as outlined on the CentOS blog <https://blog.centos.org/2022/08/centos-automotive-sig-first-year-in-review/> : We worked to define what the Automotive SIG is producing and we landed on three artifacts: - AutoSD, a CentOS-Stream based linux distribution which is the public, in-development version of the Red Hat In-Vehicle Operating System (similar to CentOS Stream for RHEL). - 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. All of this resides in a repository on gitlab, in the CentOS namespace with the infrastructure to enable CI/CD for a basic distribution. We are building a set of nightly images for different use-cases, and have a robust set of documentation at the above link. Not a lot of high-level features have been introduced over the past few months due to vacation schedules, but the distro is doing very well and now supports a SOAFEE implementation along with container support based on podman and systemd. In addition, we are pleased to have had the first contribution from outside Red Hat (thanks Volvo!). _____________________________________ 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 0

Initial support for android boot in sample images
by Alexander Larsson 02 Sep '22

02 Sep '22

I just today merged[1] initial support for android boot in the sample images. This is still somewhat experimental, but allows some level of support for aboot. The support has multiple parts: * The abootimg rpm has an app that can create aboot images. * The aboot-update rpm has integration between the kernel and aboot. It looks at the /boot/aboot.cfg file for aboot options and applies them for a kernel version producing a file /boot/aboot-${kernel_version}.img. It also hooks into the kernel rpms to run automatically when a new kernel is installed. * The osbuild-aboot rpm, which must be installed on the build host, adds some new osbuild stages that use aboot-update. (This is in a separate copr) * A new "abootqemu" target which is similar to the existing "qemu" target, but using aboot instead of grub/efi. * Support in runvm for --aboot, which uses a custom bios that supports aboot. This allows testing of the aboot-based boot. (Only on aarch64 atm.) A full example of testing this: $ sudo dnf copr enable alexl/osbuild-aboot $ sudo dnf install osbuild-aboot $ make cs9-abootqemu-minimal-regular.aarch64.qcow2 $ make qemu-u-boot-aarch64.bin $ ./runvm --aboot --arch aarch64 cs9-abootqemu-minimal-regular.aarch64.qcow2 The qemu boot output: U-Boot 2022.07 (Aug 26 2022 - 00:00:00 +0000) [...] Device 0: 1af4 VirtIO Block Device Type: Hard Disk Capacity: 8192.0 MB = 8.0 GB (16777216 x 512) ... is now current device Found Android Boot Image virtio read: device 0 block # 2048, count 131072 ... 131072 blocks read: OK Kernel load addr 0x50000000 size 10232 KiB Kernel command line: root=UUID=76a22bf4-f153-4541-b6c7-0332c0dfaeac ro loglevel=4 efi=runtime console=ttyAMA0 RAM disk load addr 0x11000000 size 25563 KiB Uncompressing Kernel Image Loading Ramdisk to fe709000, end fffff8c6 ... OK Loading Device Tree to 00000000fe606000, end 00000000fe708fff ... OK Starting kernel ... [ 0.000000] ACPI: Failed to init ACPI tables Welcome to CentOS Stream 9 dracut-057-13.git20220816.el9 (Initramfs)! [...] [1] https://gitlab.com/CentOS/automotive/sample-images/-/merge_requests/116 -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Alexander Larsson Red Hat, Inc alexl(a)redhat.com alexander.larsson(a)gmail.com

1 0

Request for ostree-compliance-mode in Automotive SIG RPM repository - ostree-compliance-mode
by Eric Curtin 26 Aug '22

26 Aug '22

Hello, I would like to request an rpm to be added to Automotive SIG RPM repository. ostree-compliance-mode is a tool designed to purge protected data, leaving the system in compliance with GPLv3. This will assist 3rd parties place non-GPLv3 applications on our OS, without necessarily having those components modifiable. Is mise le meas/Regards, Eric Curtin

2 1

Happy Anniversary, CentOS Automotive SIG!
by Jeffrey Osier-Mixon 05 Aug '22

05 Aug '22

Todays' monthly meeting was lightly attended as expected, and we didn't have a lot of technical topics to update, but I did want to send out the one thing we did cover. August marks the 1st anniversary of the CentOS Automotive SIG, and we have accomplished quite a lot over this first year. The first meeting was August 19, 2021, at which time there was no infrastructure at all and the group had just been voted into existence by the CentOS board. Now, one year later, we have a robust repository within the CentOS domain, open to contributions by the public - and indeed we had our first contributor from outside Red Hat over the past month, which is a great example of the value we hope we are bringing to automotive Linux development. In addition to the repositories, we have a strong nightly build structure providing a continuous stream of images that are easy to download and get running via QEMU or on a Raspberry Pi 4. The image uses Stream 9 components with a customized (real time) kernel, a good example of CentOS Stream based development, and a fun and interesting project. Congratulations to everyone involved with the SIG, and thanks again to CentOS for hosting it! Jeffrey "Jefro" Osier-Mixon | jefro(a)redhat.com Red Hat Office of the CTO | Sr. Principal Community Architect, Automotive

3 2

Update on the automotive-sig
by Pierre-Yves Chibon 05 Jul '22

05 Jul '22

Good Morning Everyone, Here is an update of what happened in the SIG last week: * The documentation on how to get an autosd image running on a raspberry pi 4 has been updated: https://sigs.centos.org/automotive/building/centos_stream_pi4/ * The webserver running behind https://autosd.sig.centos.org/ has been upgraded to a bigger machine using goofys for the s3 backend connection. This should make it much faster! Happy hacking! Pierre

1 0

2025

2024

2023

2022

2021

automotive-sig