Software Orchestration blueprint

fprezado commented 10 months ago

Goal

This blueprint aims to showcase an example of how a proposed in-vehicle software orchestration architecture with connectivity to the cloud can help developers build and manage complex services and applications that tackle advanced scenarios like workload orchestration, scheduling, placement and resilience. The abstraction layers provided by the blueprint aim to simplify and enhance the developer experience. These include discovery and consumption of resources and services, support for a common vehicle model to be used across vehicles, dynamic topic management for publish and subscribe of vehicle signals and synchronization of signals to a cloud digital twin.

Use Case

The system detects that a smart trailer is being connected to the car. A signal is raised to the orchestrator that a smart trailer provider and application is required to manage the smart trailer and adjust body functions and powertrain accordingly and ensure a smooth trip.*

Projects

Eclipse Bluechi, Ankaios, Chariott, Ibeji, Freyja, Agemo and Kanto

Roadmap

Phase 1: In the first phase, we will show single and multi-node orchestration through an implementation with Eclipse Ankaios and another implementation with Eclipse BlueChi.

Phases 2 and 3: Looking forward, in the second phase, we will target multi-domain orchestration and integrate with project Kanto. In the third phase, we will target the Cloud services for OTA.

Help Wanted

The blueprint will be delivered with a basic sample of how to integrate with the stack, but we have several other ideas for use cases that can be built. We are hoping to have community help during the upcoming hackathon to develop on top of this blueprint.

*We understand that there are safety and security implications with the orchestration of this use case, we will address this in phase 2.

nacidai commented 10 months ago

Thank you for your submission. Can you comment on:

who will be in charge of maintaining this blueprint and the expected members.
A list/links to the SDV projects that will be included
Other technologies worth mentioning

Also, would it be ok for you to present the blueprint at the next Blueprints zoom call (Nov 7, 3PM CEST)?

ladatz commented 9 months ago

Expected member companies: Phase 1: Microsoft, Elektrobit, Red Hat, Phase 2: ETAS, Cummins
Projects:
- Eclipse Agemo
- Eclipse Chariott
- Eclipse Freyja
- Eclipse Ibeji
- Eclipse Ankaios
- Eclipse BlueChi
- Phase 2, 3: -Eclipse Kanto -Eclipse Leda
Other technologies: For Phase 2 and 3: AUTOSAR applications (need to investigate potential collaboration with AUTOSAR and open source licensing) , Cloud connectors, OTA
Yes we can present today

nacidai commented 9 months ago

I will kickoff the voting process to make the Software Orchestration a new blueprint:

+1

iarmac commented 9 months ago

+1

windsource commented 9 months ago

+1

sophokles73 commented 9 months ago

+1

badiiennouri1987 commented 9 months ago

+1

AnotherDaniel commented 9 months ago

+1

fprezado commented 9 months ago

+1

nacidai commented 9 months ago

7 (+1), 0 (-1)

The proposal has been accepted. @fprezado @ladatz

Please provide the following details so that I can create a request at the Eclipse EMO help desk to create a repository and add the initial committers for your blueprint:

Blueprint name: Blueprint repository name: ((must be a valid github repository name) List of initial committers: (Name, Email) If they are not already, all committers will become committer members of Eclipse Foundation and accept its policies

fprezado commented 9 months ago

thanks @nacidai , all for the comments, feedback and voting.

we will reply back with the details.

ladatz commented 9 months ago

Blueprint name: Software Orchestration blueprint Blueprint repository name: software-orchestration List of initial committers: Lauren Datz, Jordan Chiu, Devin Kelley, Filipe Prezado, William Lyles, Liviu Tiganus, Holger Dormann, Oliver Klapper, Chatree Akasarn, Leonardo Rosetti, Michael Engel

@nacidai do you need email addresses or GitHub aliases for the committers?

nacidai commented 9 months ago

Blueprint name: Software Orchestration blueprint Blueprint repository name: software-orchestration List of initial committers: Lauren Datz, Jordan Chiu, Devin Kelley, Filipe Prezado, William Lyles, Liviu Tiganus, Holger Dormann, Oliver Klapper, Chatree Akasarn, Leonardo Rosetti, Michael Engel

@nacidai do you need email addresses or GitHub aliases for the committers? Yes, also in order to become committers they should have an eclipse account with the email provided and sign the ECA (eclipse committer agreement at https://portal.eclipse.org)

ladatz commented 9 months ago

@nacidai Here are the email addresses. Please let me know if you need more information

List of initial committers: Lauren Datz (ladatz@microsoft.com), Jordan Chiu (jordanchiu@microsoft.com), Devin Kelley (dekelle@microsoft.com), Filipe Prezado (fprezado@hotmail.com), William Lyles (wilyle@microsoft.com), Liviu Tiganus (liviut@microsoft.com), Holger Dormann (holger.dorman@elektrobit.com), Oliver Klapper (oliver.klapper@elektrobit.com), Chatree Akasarn (chatree.akasarn@elektrobit.com), Leonardo Rosetti (lrossett@redhat.com), Michael Engel (mengel@redhat.com)

nacidai commented 9 months ago

I have created a request with the eclipse emo helpdesk. We can follow the progress there. Please check the issue and subscribe. EMO may have questions and requests.

https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/3979

nacidai commented 9 months ago

Congrats. Your repository has been created!

https://github.com/eclipse-sdv-blueprints/software-orchestration

Happy blueprinting!

eclipse-sdv-blueprints / blueprints