SOAFEE One-Page Overview

SOAFEE

Policy / Motto?

“Cross-development is pointless and stupid when the alternative is to just develop and deploy on the same platform.” — Linus Torvalds

What is the Problem?

Code for embedded systems like those in the automotive domain has been that the software is written on the supplied API’s available in the BSP that is delivered with the selected processor, dependence on specific API’s in the underlying BSP.

We just cannot do the following Intelligent Workload Migration...

Summary

• Scalable Open Architecture For Embedded Edge
• Real-Time software architecture, including Cloud Native
• Basically extends Cloud Native architecture to Embedded Devices
• 1st priority is autonomous driving as reference

Technical Insights

• ADLINIK, OpenRobotics, Eclipse
  SOAFEE’s reference application is Open Robotics ROS 2 with Autoware.Auto, and the default ROS middleware Eclipse Cyclone DDS with iceoryx zero-copy and Zenoh V2X.
• OCI (Open Container Initiative) compatible including CRI(Container Runtime Interface), CNI(Container Network Interface) and CSI(Container Storage Interface)
• (CDI, Container Device Interface) is not listed as SOAFEE aspect, but I believe it will be. This device abstraction layer will be required as key part.
• What's missing for SOAFEE requirements?
  • as container orchestrator, IO bandwidth, execution time and cache policy.
  • as container runtime, privilege control to resource
  • VirtIO is lack of Safety, Realtime, does not cover all enough VirtIO interfaces for automotive domain.

Reference

• ADLINK Technology Hardware Reference, Ampere Altra SoC, https://www.adlinktech.com/en/soafee
• gitlab.arm.com/soafee, currently almost empty atm
• SOAFEE white paper
• arm DevSummit 2021 Cloud-Native to Car
• Scalable Open Architecture For Embedded Edge – SOAFEE