1 of 17

SOAFEE R2�Release Plan�

Aug 2022

Daniel Bernal

Daniel.Bernal@SOAFEE.IO

SOAFEE SIG

SOAFEE Special Interest Group

1

SOAFEE Special Interest Group

2 of 17

SOAFEE R2 Release Plan

Topics

  • SOAFEE R1 - A Retrospective
    • Lessons Learned
  • SOAFEE R2 - Announcement
    • What’s included in the announcement? The messaging...
      • EWAOL v1.0
      • Blueprint - AWF Open AD Kit
    • Documentation
      • gitlab.com/soafee Structure
      • Detailed docs

​

2

SOAFEE Special Interest Group

3 of 17

SOAFEE R1 Announcement – A Retrospective

What was included:

  • SOAFEE Reference Implementation: EWAOL v0.2.4 w/instructions how to build and run on AVA Dev Platform
  • Reference Application: Autoware.Auto w/instructions how-to execute on AVA Developer Platform

​

​

SOAFEE Reference Stack R1

Announcement (Oct 2021)

Application:

  • Autoware.Auto

​

Base SW Stack: Edge Workload Abstraction & Orchestration Layer (EWAOL v0.2.4)

  • Yocto Linux 
  • OCI Container Engine Runtime
  • K3s Container Orchestration Client

​

HW Platform:

  • ADLINK AVA Developer Platform (SystemReady SR)

3

SOAFEE Special Interest Group

4 of 17

SOAFEE R1 Announcement – Lessons Learned

Lesson Learned

R2 and Forward

SOAFEE R1 announced early release of EWAOL with instructions how to build and execute Autoware/EWAOL on the ADLINK AVA Dev Platform.

​

Q: What is the goal for the SOAFEE announcement?

A: Announce an iteration or next release of the “SOAFEE Reference Implementation”

Create a clear distinction between EWAOL and the application/workload used to validate/demonstrate the capabilities of EWAOL.

​

Benefits:

  • Decouples workload validation examples from reference implementation (e.g., EWAOL or others at some point)
  • Creates infrastructure to host & announce partner enabled SOAFEE reference implementations.

​

Need to establish the infrastructure on gitlab.com/soafee to scale out additional SOAFEE Ref Implementation releases and additional Blueprint releases.

We will create a SOAFEE Reference Implementation Landing Page:

​

      • What’s new?
      • Link to documentation.
      • References/links to example workloads (blueprints) used to validate the release.
          • References/links on where to find previous releases

Need to clearly establish the concept of Blueprints and explain them.

We will create a structure to scale Blueprints going forward:

  • https://gitlab.com/soafee/blueprints - A landing page where all blueprints can be found.
  • What is a Blueprint – Workload validation example of a use-case.
  • How can a SOAFEE SIG member submit/propose a new Blueprint – Join the SOAFEE Ref Impl WG

4

SOAFEE Special Interest Group

5 of 17

SOAFEE R2

EWAOL v1.0

​

  • Yocto Linux (poky)
  • Open Container Initiative (OCI) Container Engine & Runtime
  • Container Orchestration Client: K3s Container Orchestration
  • Baremetal Architecture (Native Linux)
  • Virtualization Architecture (Xen Hypervisor)
  • On-target Development Support
  • Validation Support
  • Build Support Tools (image, documentation, and QA)

​

​

HW Platform Support:

  • ADLINK AVA Developer Platform (SystemReady SR)
  • EWAOL Release support for Rock Pi 4 Platform

Open AD Kit Autonomy Blueprint

​

  • Autoware Application
  • Validated on EWAOL v1.0 running on ADLINK AVA Developer Platform

SOAFEE R2 Reference Implementation

Blueprint -

Reference Workload used for validation

5

SOAFEE Special Interest Group

6 of 17

SOAFEE R2 - Announcement

​

SOAFEE R1

Announcement (Oct 2021)

Application:

  • Autoware.Auto

​

Edge Workload Abstraction & Orchestration Layer (EWAOL) (Version 0.2.4)

  • Yocto Linux (poky)
  • OCI Container Engine
  • K3s Container Orchestration

​

HW Platform:

  • ADLINK AVA Developer Platform (SystemReady SR)

​

SOAFEE R2 Announcement

Announcement (Target – Early Aug 2022)

EWAOL v1.0

  • Includes all SOAFEE R1 Features
  • Virtualization Support (XEN Hypervisor)

​

HW Platform Support:

  • ADLINK AVA Developer Platform (SystemReady SR)
  • EWAOL Release support for RockPi

Blueprint - AWF Open AD Kit

  • Autoware Application
  • Validated on EWAOL v1.0 running on ADLINK AVA Developer Platform

SOAFEE R2 Reference Implementation

Blueprint -

Reference Workload used for validation

Clear distinction between a Blueprint and the SOAFEE reference implementation (EWAOL)

6

SOAFEE Special Interest Group

7 of 17

Edge Workload Abstraction & Orchestration Layer (EWAOL) v1.0

Arm-Based Hardware Platforms

  • ADLINK AVA Developer Platform
  • RockPi 4

Standards-Based Firmware

EWAOL v1.0

  • Yocto Linux 
  • OCI Container Engine & Runtime
  • K3s Container Orchestration Client
  • Baremetal Architecture (Native Linux)
  • Virtualization Architecture (Xen Hypervisor)
  • On-target Development Support
  • Validation Support
  • Build Support Tools (image, documentation, and QA)

Reference Implementation

Supported Platforms

7

SOAFEE Special Interest Group

8 of 17

Blueprint - Autoware Foundation (AWF) Open AD Kit

Arm-Based Hardware Platform

Standards-Based Firmware

Base SW Stack

​

  • Container Runtime
  • Container to Container Network
  • Off-platform Networking

AWF Open AD Kit

Reference Implementation

(EWAOL v1.0)

Container

Map

Container

Perception

Container

Planning

Container

Vehicle Interface

ADLINK

AVA Developer Platform

8

SOAFEE Special Interest Group

9 of 17

SOAFEE Release Messaging - Proposal

WIP by MSC

SOAFEE - Moon 2

Architecture Spec

SOAFEE - Moon 1

Open Source Ref Implementation

Blueprints

Draft

Release

AWF

Autoware.Auto

AWF

Open AD Kit

V1

EWAOL

0.2

HW: AVA Dev

EWAOL

1.0

HW: AVA Dev, Rock Pi 4

Arch

Spec

0.5

Arch

Spec

1.1

Eclipse SDV Chariot V1

EWAOL

2.0

HW: x

Arch

Spec

1.0

AWF

Open AD Kit

V2

RedHat IVOS

1.0

HW: x, y

Arch

Spec

1.2

SOAFEE R1

EWAOL 3.0

Eclipse SDV

Chariot V3

AWF Open AD Kit

V3

Arch

Spec

1.3

EWAOL 4.0

RedHat IVOS Y

SUSE SDV Y

Ubuntu SDV Y

Panasonic IVI AGL V2

Other Blueprints

RedHat IVOS X

SUSE SDV X

Ubuntu SDV X

AWF Open AD Kit

V3

Eclipse SDV

Chariot V2

Panasonic IVI AGL V1

Other Blueprints

Basic Release Infrastructure must support:

​

  • New and updated SOAFEE reference implementations?
  • New hardware/platform support by reference implementations? 
  • New blueprints added with support for one to many soafee reference implementations with update capability?

A proposal was made to name the SOAFEE Architecture release after the moons of Mars (vs. R2) for maximum flexibility on announcements going forward.

Do we need to release a draft spec? If so, when?

Partner Implementations

Arch

Spec

2.0

Eclipse SDV Chariot V2

9

SOAFEE Special Interest Group

10 of 17

SOAFEE Release Documentation

  • Long term goal is to land all SOAFEE documentation and repos on:
    • https://soafee.io - SOAFEE Website
    • https://gitlab.com/soafee - SOAFEE Documentation and Repos
    • readthedocs - EWAOL Documentation

​

  • New Documentation Needed for:
    • SOAFEE R2 Release Details - Daniel B. Action Item
    • Blueprint - AWF Open AD Kit Details – Kasper Action Item

​

  • Requires Migration of:
    • EWAOL Documentation, previously on https://ewaol.docs.arm.com/en/v1.0/

​

  • Deprecating the following:
    • SOAFEE R1 Documentation, previously on https://gitlab.arm.com/soafee - [deprecated]

​

10

SOAFEE Special Interest Group

11 of 17

SOAFEE R2 – Documentation Detail & Status

Document

Location

Owner

Status

SOAFEE Reference Implementations - Landing Page

Daniel

Daniel B. will create

draft:

tbd

SOAFEE R1 Release Page

Daniel

Anmar suggests we deprecate.

draft:

​

SOAFEE R2 Release Announcement - Page

Daniel

Draft created.

draft:

soafee_r2_release.md

SOAFEE Blueprints - Landing Page

Kasper/Daniel

Kasper will create

draft:

​

Blueprint - AWF Open AD Kit / V1

Kasper

Kasper will review what Anmar/Leo have created.

draft:

​

11

SOAFEE Special Interest Group

12 of 17

SOAFEE Post R2 – Documentation & Website Cleanup

Document

Location

Owner

Status

SOAFEE Web Content

​

​

​

​

SOAFEE EWAOL Docs

​

Plan to migrate to another site

​

​

​

​

​

​

​

​

​

​

​

​

​

​

​

​

12

SOAFEE Special Interest Group

13 of 17

Thank You

Danke

Gracias

谢谢

ありがとう

Asante

Merci

감사합니다

धन्यवाद

Kiitos

شكرًا

ধন্যবাদ�תודה

SOAFEE Special Interest Group

13

SOAFEE Special Interest Group

14 of 17

SOAFEE Release Messaging - Proposal

WIP

Architecture Spec

SOAFEE R2

Open Source Ref Implementation

Blueprints

Draft

Release

AWF

Autoware.Auto

AWF

Open AD Kit

V1

EWAOL

0.2

HW: AVA Dev

EWAOL

1.0

HW: AVA Dev, Rock Pi 4

Arch

Spec

0.x

Arch

Spec

1.0

Eclipse

SDV Chariot

V1

Eclipse

SDV Chariot

V1

EWAOL

2.0

HW: x

Arch

Spec

0.y

AWF

Open AD Kit

V2

RedHat IVOS

1.0

HW: x, y

Arch

Spec

1.x

SOAFEE R1

EWAOL 3.0

Eclipse SDV

Chariot V3

AWF Open AD Kit

V3

Arch

Spec

1.y

EWAOL 4.0

RedHat IVOS Y

SUSE SDV Y

Ubuntu SDV Y

Panasonic IVI AGL V2

Other Blueprints

RedHat IVOS X

SUSE SDV X

Ubuntu SDV X

AWF Open AD Kit

V3

Eclipse SDV

Chariot V2

Panasonic IVI AGL V1

Other Blueprints

Basic Release Infrastructure must support:

​

  • New and updated SOAFEE reference implementations?
  • New hardware/platform support by reference implementations? 
  • New bluerprints added with support for one to many soafee reference implementations with update capability?

We propose we call it a SOAFEE Announcement (vs. R2) for maximum flexibility on announcements going forward.

Do we need to release a draft spec? If so, when?

Partner Implementations

14

SOAFEE Special Interest Group

15 of 17

SOAFEE Release Messaging - Proposal

Architecture Spec

SOAFEE R2

Reference Implementations

Blueprints

Draft

Release

AWF

Autoware.Auto

AWF

Open AD Kit

V1

EWAOL

0.2

​

HW: AVA Dev

EWAOL

1.0

​

HW: AVA Dev, Rock Pi 4

Arch

Spec

0.x

Arch

Spec

1.0

Eclipse

SDV Chariot

V1

Eclipse

SDV Chariot

V1

EWAOL

2.0

HW: x

Arch

Spec

0.y

AWF

Open AD Kit

V2

RedHat IVOS

1.0

HW: x, y

Arch

Spec

1.x

SOAFEE R1

EWAOL 3.0

Eclipse SDV

Chariot V3

AWF Open AD Kit

V3

Arch

Spec

1.y

EWAOL 4.0

RedHat IVOS Y

SUSE SDV Y

RTOS SDV Y

Panasonic IVI AGL V2

Other Blueprints

RedHat IVOS X

SUSE SDV X

RTOS SDV X

AWF Open AD Kit

V3

Eclipse SDV

Chariot V2

Panasonic IVI AGL V1

Other Blueprints

Basic Release Infrastructure must support:

​

  • New and updated SOAFEE reference implementations?
  • New hardware/platform support by reference implementations? 
  • New bluerprints added with support for one to many soafee reference implementations with update capability?

We propose we call it a SOAFEE Announcement (vs. R2) for maximum flexibility on announcements going forward.

Do we need to release a draft spec? If so, when?

15

SOAFEE Special Interest Group

16 of 17

SOAFEE Reference Implementation - Release Spaghetti Problem Space

EWAOL

(v1-vn)

SUSE

(v1-vn)

Red Hat

(v1-vn)

Ubuntu

(v1-vn)

SOAFEE Reference Implementations ( R1 - Rn )

RTOSn

(v1-vn)

BP1

(v1-vn)

BP2

(v1-vn )

BP3

(v1-vn )

BP4

(v1-vn )

Blueprints

BPn

(v1-vn )

​

A blueprint needs to be based on at least one of the supported SOAFEE reference implementations )

Reference Hardware

HW1

HW2

HWn

A SOAFEE ref implementation needs to support one or many hardware platforms part of SOAFEE integration lab. The ref implementations as decoupled from blueprints

A blueprint needs to support atleast one of the platforms part of SOAFEE integration lab.

Should we have a public release train for each ref implementation ?

Should we have a release train for SOAFEE Reference IMplementation ( R1 - Rn ) comprising a stable version of distro specific ref implementation ?

Should we have independent BP release supporting specific hardware and ref implementations or as part of SOAFEE Reference Implementation R1-Rn support specific stable distros, blueprints and hardware aka Akraino pattern ?

16

SOAFEE Special Interest Group

17 of 17

Blueprint - Generic

Hardware (physical, cloud or virtual)

Standards-Based Firmware

​

​

​

Reference Implementation

​

Domain-Specific Application

17

SOAFEE Special Interest Group