SlapOS currently supports most GNU/Linux distributions: Debian, Fedora, CentOS, SuSE, Ubuntu, etc. This makes SlapOS compatible with virtually any cloud or hosting company, and with any server hardware. However, none of those distributions can be considered seriously for an embedded system because of a few limitations:
Those limitations mean that a server may no longer reboot after an upgrade (non safe upgrade procedure) and that nobody knows what is actually running on the server (system image is not read-only). This prevents to use SlapOS in applications that require "zero remote access" (industrial, high security) or "system compliance" (high security, certification).
We hope to solve those issues by porting SlapOS to Yocto. More precisely, what we hope to get by order of priority is:
Our goal is not unique in the industry:
We could have considered to simply fork CoreOS but CoreOS is not suitable for embedded systems which are one of the target applications of SlapOS for Edge Computing. We therefore prefer to focus on Yocto, the industry standard for embedded Linux systems. Yet, many ideas and possibly software can be reused by learning from ChromeOS, CoreOS and from recent experiments based on Coreboot bootloader. We strongly recommend reading the article "U-root: A Go-based, Firmware Embeddable Root File System with On-demand Compilation" that goes one step beyond in liberating the boot process. Jean-Marie Verdun's comments on Facebook are also worth reading. Jean-Marie is one of the founders of OCP.
The port of SlapOS to Yocto will be managed according to the following steps:
We hope that the first steps can quickly be used in production on OCP hardware managed by VIFIB withing a few weeks or months and that running on ARM can be achived within months.