Feature Request: AutoSD Development Platform

[odra]

AutoSD Development Platform Feature Request

Abstract

AutoSD is the upstream binary distribution that serves as the public, in-development preview of Red Hat In-Vehicle Operating System (OS). AutoSD is downstream of CentOS Stream, so it retains most of the CentOS Stream code with a few divergences, such as an optimized automotive-specific kernel rather than CentOS Stream’s kernel package. Red Hat In-Vehicle OS is based on both AutoSD and RHEL, both of which are downstreams of CentOS Stream.

Motivation

Use AutoSD as a development platform for the S-CORE project, leveraging its built-in features, to build test and run the S-CORE stack.

This section is split into sub-sections to highlight AutoSD's main features.

Mixed Critical Orchestration

AutoSD ships a mixed critical orchestration stack with Systemd, Podman, Eclipse BlueChi and QM (containerized environment for QM workloads), which is tightly coupled to the operating system.

AutoSD's QM (containerized) environment is stored in its own partition by default.

More details about Eclipse BlueChi and QM can be found at:

• https://bluechi.readthedocs.io/en/latest/
• https://github.com/containers/qm

Supported Architectures and Platforms

AutoSD images are constantly built and tested against both x86_64 and aarch64 architectures through the Automotive SIG pipelines. It’s also built/tested against the following platforms:

• Texas Instruments:
  • BeaglePlay (beagleplay)
  • SK-AM62x Sitara (am62sk)
  • SK-AM69 Jacinto (am69sk)
  • TDA4 EVM (tda4vm_sk)
  • J784S4 EVM (j784s4evm)
• Renesas R-Car S4
• NXP S32G-RDB3
• Qualcomm Snapdragon Ride SX 4.0
• Raspberry pi 4

The following "virtual platforms" are also supported:

• QEMU
• AWS
• Azure

Further details at https://sigs.centos.org/automotive/provisioning/.

Testing Tools

AutoSD contains a collection of tools for Perf & Scale tests that can be used to test its S-CORE image: https://sigs.centos.org/automotive/performance_monitoring_with_pcp/#arcaflow-workflow.

Rationale

The proposal is to maintain a repository with manifest AutoSD files to build an image tailored for the S-CORE project, the repository is currently maintained within the CentOS Automotive SIG organization in Gitlab: https://gitlab.com/CentOS/automotive/autosd-image-score, but it could be moved to the S-CORE Github organization as well.

There is also the option to test the S-CORE task in some of AutoSD’s supported hardware, if there is interest (needs further discussion on what and how to test).

Specification

Possible impacted areas of the specification:

• Operating System
• Mixed Critical Orchestration

Backwards Compatibility

Not needed since it’s a new development platform to be included.

Security Impact

The platform can help on some security tests, since it uses several SELinux policies (these can be provided if needed).

Safety Impact

No impact since it’s a development platform.

License Impact

No impact, image manifest files can be licensed under Apache 2.0.

How to Teach This

Contribute guides and docs to the S-CORE architecture website (suggestion: create a “platforms” section).

Rejected Ideas

Open Issues

Footnotes

[FScholPer]

Can you please explain your proposal more in detail and bring that into the architecture community to discuss

[odra]

I've updated the issue request text with the proper template.

[FScholPer]

Perfect thank you. Next step would be to create a pull request with sphinx needs requirements which fits to that feature request. Than it can be discussed in the next workshop and a call for contributions can take place.

[odra]

Is this the same workshop to happen in July? Could I participate?

[FScholPer]

It is the architecture community workshop which takes places every quarter. Next one takes place in Ulm Germany 08th July until 10 of July. I think onsite and hybrid will be possible. Do you have any user in Slack?

[odra]

My slack username is "lrossett"

[FScholPer]

You should have the invite now @odra