Reviews run for a minimum of one week. The outcome of the review is decided on this date. This is the last day to make comments or ask questions about this review.
Eclipse AutoSD Automotive Integration Project
The CentOS Automotive SIG[0] is responsible for producing AutoSD (Automotive Stream Distribution), a linux distro tailored for the automotive industry; AutoSD has a “distributed” nature, meaning that it does not offer a “base image” as most binary linux distros, but a set of pre-built binaries and tools for users to build their own images.
Eclipse SDV has several automotive projects, some of them fit very well together, which usually results in an Eclipse SDV blueprint. This means that both projects and blueprints need automotive platforms, i.e an operating system, to build, run and test said projects or use-cases.
AutoSD, being the functional precursor of Red Hat’s certified automotive distro, is a good match to be considered and used as an integration (as far as an OS goes) project by the Eclipse SDV community.
It’s important to highlight that Eclipse AutoSD Automotive Integration Project is not about donating any existing CentOS RPMs, images, etc. The project would still rely on upstream RPMs from the CentOS automotive SIG while maintaining image building manifests in an Eclipse SDV integration project (and any specialized tooling created for this project under the Eclipse SDV umbrella).
[0] - https://sigs.centos.org/automotive/
Eclipse AutoSD Automotive Integration Project provides manifest files and tooling to build one or more AutoSD images to build, run and test Eclipse SDV projects and blueprints, allowing one to easily swap deployed components, create blueprints and so on. Either locally or in a CI/CD pipeline.
Eclipse AutoSD Automotive Integration Project uses an AutoSD image, built and tailored for its community, to run and test both Eclipse SDV projects and blueprints.
Eclipse AutoSD Automotive Integration Project offers a foundation for projects to build, run and test their stack, components and services, including blueprints.
The image setup will expose projects into thinking how their projects or blueprints would work in an Mixed Critical Orchestration[0] architecture.
Several upstream tools from the CentOS Automotive SIG can used, from building images[1] to performance testing[2], but this integration project could also provide its own set of specialized tools for Eclipse SDV, to ease the process of deploying blueprints into this reference AutoSD image and so on.
This integration project gets several supported platforms (read boards) for free[3], including virtual ones, such as AWS and Azure, allowing the possibility of running blueprints tests in said cloud providers.
[0] - https://sigs.centos.org/automotive/features-and-concepts/con_mixed-criticality/
[1] - https://gitlab.com/CentOS/automotive/src/automotive-image-builder
[2] - https://sigs.centos.org/automotive/performance_monitoring_with_pcp/#arcaflow-workflow
[3] - https://sigs.centos.org/automotive/provisioning/
Not an issue per se, as mentioned in other sections of this proposal, packages and build tools would be installed/used from the CentOS Automotive SIG (and owned by the SIG). All packages and tools are open-sourced.
I want to craft an AutoSD image that is part of Eclipse SDV, tailor it for the group’s specific needs, so it can provide a solid Linux operating system foundation for the SDV community as an integration project.
AutoSD can expose projects to an architecture that is very close to a production one, in terms of Mixed Critical Orchestration (QM and non QM environments), IPC, Linux containers, cloud CI and native practices, etc.
- Support all blueprints within the repository;
- Make it a good development platform for hackathons;
- Engage with other projects and help them use it;
- Empower blueprint creation by providing an integration project;
- Create tools and scripts to easily load a blueprint into an AutoSD image without much burden to projects/blueprints maintainers.
I would like to complete the process by the end of Q3, if possible.
We already have a working image build for the service-to-signal blueprint, the following months will be about supporting other blueprints.
Repository URL: https://gitlab.com/CentOS/automotive/autosd-image-eclipse-sdv
The above repository contains:
- Manifests files to build an AutoSD image;
- A base clean image definition in the main branch;
- A “eclipse-sdv-blueprints/service-to-signal” branch which runs that blueprint.
- Log in to post comments
Eclipse AutoSD Automotive Integration Project uses an AutoSD image, built and tailored for its community, to run and test both Eclipse SDV projects and blueprints.
Eclipse AutoSD Automotive Integration Project offers a foundation for projects to build, run and test their stack, components and services, including blueprints.
The image setup will expose projects into thinking how their projects or blueprints would work in an Mixed Critical Orchestration[0] architecture.
Several upstream tools from the CentOS Automotive SIG can used, from building images[1] to performance testing[2], but this integration project could also provide its own set of specialized tools for Eclipse SDV, to ease the process of deploying blueprints into this reference AutoSD image and so on.
This integration project gets several supported platforms (read boards) for free[3], including virtual ones, such as AWS and Azure, allowing the possibility of running blueprints tests in said cloud providers.
[0] - https://sigs.centos.org/automotive/features-and-concepts/con_mixed-criticality/
[1] - https://gitlab.com/CentOS/automotive/src/automotive-image-builder
[2] - https://sigs.centos.org/automotive/performance_monitoring_with_pcp/#arcaflow-workflow
[3] - https://sigs.centos.org/automotive/provisioning/
- Log in to post comments