This challenge is about being creative while using Eclipse SDV projects to provide your own solution architecture and implementattion.
The only hard requirement is to use at least one Eclipse SDV project.
The challenge provides a basic environment using devcontainers with:
- AutoSD (CentOS Stream 9 Automotive Distribution) as the base OS;
- Systemd + Podman + Eclipse BlueChi as the workload orchestration stack;
- Eclipse uProtocol as the service mesh spec;
- Eclipse Kuksa Databroker as the automotive messaging databroker;
- Optional Openshift access if needed.
- Use at least one Eclipse SDV project;
- Bonus points if you use 2+ projects together;
- Provide an architecture diagram about your solution;
- You can get inspired by some of the official Eclipse SDV Blueprints;
- Do not rely on any closed source software.
config
: configuration files used by applicationsworkloads
: service workloads used by systemd, thse files are also mounted in /etc/containers/systemdsrc
: your source code
Simply run:
devcontainer up --workspace-folder .
You need to --docker-path
if using podman (or something else that is not docker):
devcontainer up --docker-path=$(which podman) --workspace-folder .
- Ensure that the Remote Development extension installed in VSCode.
Devcontainers upstream documentation:
You can use the VSCode devcontainer extension to start your containerized development environment.
cd <absolute/path/to>/maestro-challenge/eclipse-bluechi
code .
VSCode detects automatically that a .devcontainer
folder exists inside this subfolder.
Please confirm the dialog to reopen VSCode inside the devcontainer.
Afterwards, open a new terminal inside the devcontainer in VSCode.