Mission impossible? How to realize a reproducible and a flexible system integration method for the SoDeV

The SoDeV is an open-source reference Software Defined Vehicle (SDV) platform. It's developed by the Automotive Grade Linux (AGL) SoDev project. It aims to de-fact standard for the SDV platform. The SoDeV platform is built on a hypervisor-based host environment and hardware decoupled guest VMs with Virt IO infrastructures. The example of those guest VMs are AOSP, AGL In Vehicle Infotainment(IVI), Instrument Cluster (IC), gateway, real-time Linux-based runtime environment and RTOS-based runtime environment. From our point of view, "reproducible" is a high-priority topic. From the SoDeV developer's point of view, we need a method for the same environment creation to share the common development environment. From the SoDeV user point of view, we need to reproduce the SoDeV platform in our own environment to evaluate, modify and more. The AGL has a common reproducible integration tool called Yocto. It already has a host and guest co-build method called multiconfig. On the other hand, that requires complex configuration. It's a big barrier for the SoDeV developer and user. In this session, I'm talking about an idea for how to fix this issue. This talk includes my investigation, trial and consideration. It's common knowledge outside the automotive field. Because the same issue exists in IoT, Industrial and other fields.