March 2022 - automotive-sig - lists.centos.org

Weekly update on the automotive-sig
by Pierre-Yves Chibon 25 Mar '22

25 Mar '22

Good Morning Everyone, So here are some of the changes that we have worked on over this week: * We can now build from gitlab.com/redhat/automotive in CBS (cbs.centos.org), note that we want to move to gitlab.com/centos/automotive as soon as the authentication questions between gitlab and the CentOS account system are solved. * Repository structure for AutoSD has been simplified. It used to include the CentOS repository from which the RPMs composing AutoSD had been pulled but that was not necessary and ended up making AutoSD split across multiple repositories instead of having just one. This is now fixed: https://autosd.sig.centos.org/AutoSD-9/latest/cs9/ (as I write this email I realize that we still have some redundancy in the path here...) * Remote-build has been improved to make it easier to run, now all you need is to write your configuration file and ensure you have podman installed on the targeted hosts! The client handles the rest. Sources: https://github.com/pypingou/remote_builder * Increased the size of the `/boot` partition on our sample images to 300M so it has enough space to install up to 3 kernels. * The rpm repository moved from the folder `product-builds` to `AutoSD-9` at: https://autosd.sig.centos.org/ Happy hacking! Pierre

1 0

Weekly update on the automotive-sig
by Pierre-Yves Chibon 18 Mar '22

18 Mar '22

Good Morning Everyone, So here are some of the changes that we have worked on over the last couple of weeks: * We got a sub-domain for AutoSD, so you can browse it at: https://autosd.sig.centos.org/ * We kept on working on allowing a new lookaside cache structure on CentOS' infrastructure, giving SIGs more flexibility on their workflow (cf the discussion on the centos-devel list) * We worked on some sample containers interacting via SOME/IP, cf: https://lists.centos.org/pipermail/centos-automotive-sig/2022-March/000085.… * We have a new tool called runvm in the repo which makes it easier to run images with qemu * Our manifest now have a variable you can use if you want to add extra repositories (in addition to extra packages) when building images. It will go something like: `make cs9-qemu-minimal-regular.aarch64.qcow2 DEFINES='extra_repos=[{"id":"foo","baseurl":"http://foo"}] extra_rpms=["some","rpms"]'` (documentation will be updated shortly) Happy hacking! Pierre

1 0

Office hours notes & new meetings pages
by Jeffrey Osier-Mixon 17 Mar '22

17 Mar '22

Hi all - you can find past CentOS Automotive SIG meeting recordings, as well as information on upcoming meetings and events, on this page: https://wiki.centos.org/SpecialInterestGroup/Automotive/Meetings Thanks to everyone who made it to today's office hours, where we discussed the current technical status as well as future options for hardware and board support. In particular, there was an active discussion around the best ways to accommodate custom kernels and long term support - thanks to Fulup and Stephane for a very interesting topic. I have started a wiki page specifically to discuss & track hardware ideas here: https://wiki.centos.org/SpecialInterestGroup/Automotive/Hardware So please feel free to log in and contribute, both here and elsewhere in the wiki. Thanks & see you all for the next meeting on April 8 Jeffrey "Jefro" Osier-Mixon | jefro(a)redhat.com Red Hat Office of the CTO | Sr. Principal Community Architect, Automotive

1 0

Using containers in automotive
by Alexander Larsson 17 Mar '22

17 Mar '22

I talked earlier here about the work I was doing to improve the container sample image in the automotive sig repo. Well, today I landed the initial version of this in gitlab. Check out the docs here: https://sigs.centos.org/automotive/building/containers/ and: https://gitlab.com/redhat/automotive/automotive-sig/-/blob/main/sample-apps… Basically it create some "automotive-like" apps that use SOME/IP to talk to each other, then embed these apps into containers and run then as system services under systemd which are automatically started at boot. There is even some custom selinux policies to manage the vsomeip socket file access. Check it out and play with it. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Alexander Larsson Red Hat, Inc alexl(a)redhat.com alexander.larsson(a)gmail.com

1 0

Linux on vehicles vs Kubernetes on vehicles
by Ali Ok 10 Mar '22

10 Mar '22

Hi, I recently read a number of articles about how to offload workloads onto containers that run on vehicles. TheChief IO article here [0] summarizes some of the things tried out there and these are the experiments I've read in detail: - Mercedes-Benz did a POC [1] where they run containers in a vehicle to run relevant tasks. The focus here is on the development and CI/CD of these software. - Denso had a similar POC [2] [3]. They ran an entire Kubernetes cluster in the vehicle. Again, the focus here is the development ease and CI/CD. Development teams simply develop and distribute software just like a web application. There's also mentions of used concepts like digital twins, request queuing (in the vehicle when offline) and few other interesting concepts. How do these efforts align or relate with the automotive initiative? What I understand from CentOS automotive SIG and the POCs I mentioned above is that there are a lot of overlapping areas (being independent of the underlying hardware, faster software distribution, etc.) done in different levels (OS/Kube). Context: I am a Knative (https://knative.dev) contributor at Red Hat. I was thinking about experimenting with Knative Eventing on the far edge, or even better, mentor a Google Summer of Code contributor this summer for that, and later I found out about the experiments done with Kubernetes on vehicles. [0] https://thechief.io/c/editorial/how-kubernetes-is-shaping-the-future-of-car… [1] https://customers.microsoft.com/en-us/story/784791-mercedes-benz-r-and-d-cr… [2] https://kubernetes.io/case-studies/denso/ [3] https://www.denso.com/jp/ja/-/media/global/business/innovation/review/25/pa…

3 4

Weekly update on the automotive-sig
by Allison King 04 Mar '22

04 Mar '22

Hello Everyone, So here are some of the changes that we have worked on over the last few weeks: - We have added the kernel-automotive package to the content definition available in content resolver: https://tiny.distro.builders/view--automotive-view.html - We have introduced the Automotive Stream Distribution as the public, in development, version of the Red Hat automotive product: - https://lists.centos.org/pipermail/centos-automotive-sig/2022-March/000073.… - https://blog.centos.org/2022/03/centos-automotive-sig-announces-new-autosd-… - The automotive SIG documentation has been updated to mention Automotive Stream Distribution, see: https://sigs.centos.org/automotive - We are working on enabling a new structure in CentOS’ lookaside cache, to give more flexibility to the SIGs’ workflows - We have a dedicated channel on Matrix: https://matrix.to/#/#centos-automotive-sig:matrix.org You can use: https://chat.fedoraproject.org if you are not already a matrix user. It’ll allow you to use for CentOS account (which is also a Fedora account since Fedora and CentOS share their account systems). Happy hacking! Allison -- *Allison King* Technical Project Manager, In-Vehicle OS Red Hat <https://www.redhat.com/> alking(a)redhat.com <https://red.ht/sig>

1 0

CentOS Automotive SIG - Matrix room available
by Jeffrey Osier-Mixon 03 Mar '22

03 Mar '22

Hi all - as we discussed in the meeting today, I have been setting up a Matrix room for synchronous communications. We have also had an IRC room, but it was little used and is now deprecated in favor of Matrix. You can join this room here: https://matrix.to/#/#centos-automotive-sig:matrix.org Please let me know if you have any questions or difficulty joining Jeffrey "Jefro" Osier-Mixon | jefro(a)redhat.com Red Hat Office of the CTO | Sr. Principal Community Architect, Automotive

2 2

Re: [Centos-automotive-sig] [CentOS-devel] CentOS Automotive SIG meeting this week
by Jeffrey Osier-Mixon 02 Mar '22

02 Mar '22

Hi Neal - Pierre will have an update on this shortly Jeffrey "Jefro" Osier-Mixon | jefro(a)redhat.com Red Hat Office of the CTO | Sr. Principal Community Architect, Automotive On Tue, Mar 1, 2022 at 11:49 AM Neal Gompa <ngompa13(a)gmail.com> wrote: > On Tue, Mar 1, 2022 at 1:56 PM Jeffrey Osier-Mixon <jefro(a)redhat.com> > wrote: > > > > Hi all - just a quick reminder that the next SIG meeting is tomorrow, > March 2, at 1500 UTC (10am EDT, 4pm CET). We will talk about the > establishment of the AutoSD distro and how to use it. > > > > RSVP is not necessary, and everyone is welcome to join. The meeting will > be held via Google Meet at this link: > > > > https://meet.google.com/hkx-btgd-dyc > > > > Please let me know if you would like to be added to the invitation going > forward. > > > > What's the AutoSD distro? > > > -- > 真実はいつも一つ！/ Always, there's only one truth! > _______________________________________________ > CentOS-devel mailing list > CentOS-devel(a)centos.org > https://lists.centos.org/mailman/listinfo/centos-devel >

1 0

CentOS Automotive SIG meeting this week
by Jeffrey Osier-Mixon 01 Mar '22

01 Mar '22

Hi all - just a quick reminder that the next SIG meeting is tomorrow, March 2, at 1500 UTC (10am EDT, 4pm CET). We will talk about the establishment of the AutoSD distro and how to use it. RSVP is not necessary, and everyone is welcome to join. The meeting will be held via Google Meet at this link: https://meet.google.com/hkx-btgd-dyc Please let me know if you would like to be added to the invitation going forward. best, Jeffrey "Jefro" Osier-Mixon | jefro(a)redhat.com Red Hat Office of the CTO | Sr. Principal Community Architect, Automotive

1 0

Introducing the Automotive Stream Distribution
by Pierre-Yves Chibon 01 Mar '22

01 Mar '22

Good Morning Everyone! When the Automotive SIG was launched last August we knew we wanted to build a place where we could gather inputs and build a community around software for the automotive industry and link these with the Red Hat and CentOS ecosystems. As Red Hat has been working on defining its automotive product, it has become clear that having a public, in development, version of this product would be beneficial. The idea would be to have it seating between the Automotive SIG and the Automotive product. This project has been named: Automotive Stream Distribution It is meant to be to the automotive product what CentOS Stream is to RHEL. Like CentOS Stream, Automotive Stream Distribution will be opened to contributions, using similar mechanisms. On Wednesday March 2nd at 15:00 UTC, we will have our SIG meeting, during which we will discuss the Automotive Stream Distribution as well, so join us there or here! Looking forward to hear your thoughts, Pierre

1 0

2024

2023

2022

2021

automotive-sig March 2022