The Edge Workload Abstraction and Orchestration Layer (EWAOL) project provides users with a standards based framework using containers for the deployment and orchestration of applications on edge platforms. Under this approach, a full software stack is divided into the following software layers:

  • Workloads: Applications deployed using containers. These are the users of the EWAOL. Note that the EWAOL project does not provide any workload containers.

  • Linux based Filesystem: This is the main component provided by the EWAOL project. It contains primarily the container engine and its run-time dependencies.

  • System software: Platform specific software composed of firmware and operating system. EWAOL does not provide the system software but uses meta-arm and meta-arm-bsp to provide an example reference stack using the N1SDP platform.

EWAOL is the reference implementation for SOAFEE (Scalable Open Architecture For Embedded Edge), the Arm lead industry initiative for extending cloud-native software development to automotive, with a special focus on real-time and functional safety. For more details, please see http://soafee.io.

More specifically, the meta-ewaol repository contains Yocto layers, configuration files, and tools to support building and validating EWAOL functionalities.


Users of this software stack must consider safety and security implications according to their own usage goals.

High-Level Architecture


The EWAOL images include the following major features:

  • Based on poky.conf distro

  • Systemd as init system

  • RPM as the package management system

  • Docker or Podman as container engine

  • runc-opencontainers as the OCI container runtime

  • Development and Test images flavors

Repository Structure

The high-level structure of the meta-ewaol repository is as follows:


Yocto layer that provides the top-level image recipes and general policies available to be implemented as a EWAOL project distribution.


Directory that contains kas configurations files for building EWAOL images.


Yocto layer that provides recipes and configuration to enable the validation of images built for the EWAOL project.


Directory that provides documentation for the meta-ewaol repository.


Directory that provides tools that perform quality-assurance checks on the repository as well as tools and scripts to support EWAOL images builds.

Layer Dependencies

The repository contains Yocto layers that require dependencies as follows. The layers revisions are related to the EWAOL v0.2.4 release.

The meta-ewaol-distro layer depends on:

URI: git://git.yoctoproject.org/poky
layers: meta, meta-poky
branch: hardknott
revision: 269265c00091fa65f93de6cad32bf24f1e7f72a3

URI: git://git.openembedded.org/meta-openembedded
layers: meta-filesystems, meta-networking, meta-oe, meta-perl, meta-python
branch: hardknott
revision: f44e1a2b575826e88b8cb2725e54a7c5d29cf94a

URI: git://git.yoctoproject.org/meta-security
layers: meta-security
branch: hardknott
revision: 16c68aae0fdfc20c7ce5cf4da0a9fff8bdd75769

URI: git://git.yoctoproject.org/meta-virtualization
layers: meta-virtualization
branch: hardknott
revision: 7f719ef40896b6c78893add8485fda995b00d51d

The meta-ewaol-tests layer depends on:

URI: git://git.yoctoproject.org/poky
layers: meta
branch: hardknott
revision: 269265c00091fa65f93de6cad32bf24f1e7f72a3

Repository License

The software is provided under an MIT license (more details in License).

Contributions to the project should follow the same license.

Contributions and Bug Reports

This project has not put in place a process for contributions currently.

For bug reports, please submit an Issue via GitLab.

Feedback and support

To request support please contact Arm at support@arm.com. Arm licensees may also contact Arm via their partner managers.