In August 2021, the CentOS Automotive SIG launched and held its first meeting with 36 participants. We had no infrastructure, no solid architectural plans, and no documentation - just a very motivated group that very quickly grew beyond Red Hat and into the automotive community.
Things have certainly changed since then! Technical lead Pierre-Yves Chibon has provided a list of the many accomplishments over the past year:
- 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.
- We created a repository on gitlab, with the infrastructure to enable CI/CD for a basic distribution.
- We worked with the CentOS Infrastructure team to enable the use of gitlab namespaces for SIGs under the main “CentOS” namespace on gitlab.com. Documentation available
- We worked with the CentOS Infrastructure team to enable flat dist-git layout, allowing easy backporting of work done in Fedora but also a consistent developer experience for people working on Fedora, CentOS-stream and in the Automotive SIG.
- Similarly, we've worked with the CentOS Infrastructure team to allow the lookaside cache used by SIGs to support the same structure as the lookaside cache used in Fedora and in CentOS Stream. All of this work is now available to all CentOS SIGs (as opt-in) and is fully documented.
- We picked the Raspberry Pi 4 as our first demo hardware to support as it is (well, as it was…). We have included support for this hardware in the kernel-automotive package available both in the Automotive SIG RPM repository as well as in AutoSD itself.
- We are building a set of nightly images for different use-cases.
- For every merge-request opened against the repository hosting the definition of our sample images, we have CI running,validating that the changes we make do not break the building of our images
- Finally, we worked on documenting a large number of use cases, such as:
While we are proud of this work so far, it is just the beginning as we develop our relationships with other communities, including SOAFEE and Eclipse SDV, and further refine AutoSD. We hope to see you at a future meeting, or on our mailing list and Matrix chat.