eclipse-leda / leda Goto Github PK

It would be great to have a printout of the Leda Cheatsheet for hackathons, e.g. DIN A0 or letter-size PDF.

It should contain:

• Title "Eclipse Leda - Hackathon Cheatsheet"
• Empty space for hackathon organizers / event specific information (wifi credentials, pre-configured Device IDs etc.)
• Small Leda Project Logo and project URL (QR), short description, date of "Last Updated" or version number
• Most common commands (sdv-... scripts, wifi setup, keyboard layout, network config, databroker-cli, ...)
• High-level architecture / components on the quickstart image
• Short descriptions and/or screenshots of kantui displaying the standard set of containers
• Standard system configuration information (e.g. linux user password, folders where to look for containers, network configuration)
• First steps, e.g. how to connect to Wifi
• References to COVESA VSS, Kanto, Kuksa, Velocitas

Hello,

I would like to provision additional containers to a fresh installation of Eclipse Leda (0.1.0+). At the moment, my approach is to write my own container manifests and manually copy them to /data/var/containers/manifests and wait for Eclipse Kanto to detect the new manifests and start the described container.

Following the documentation in https://eclipse-leda.github.io/leda/docs/device-provisioning/vehicle-update-manager/ my understanding is that the "Leda-way" of doing this container update, would be to write or generate a new desired state configuration with the additional containers and send it to the VUM.

How would an example message to the VUM and the configuration for the Container Update Manager look like in this scenario?
Is there a way to retrieve the current state as a message/file so one can extend that state instead of destroying the current state by applying changes?

Based on the warning in the linked documentation page, and because Leda switched to Eclipse Kanto for the container execution my current assumption is that the example deployment specification in https://eclipse-leda.github.io/leda/docs/device-provisioning/vehicle-update-manager/vehicle-update-manager-configuration/ is not applicable anymore because it assumes Kubernetes for the container orchestration. Is my assumption correct?

When opening https://eclipse-leda.github.io/ a 404 appears.
There should be a redirect to /leda

Note: full page is generated by GH Pages, need to check how to add the root index page.

Hello,

I would like to setup a fresh Leda installation for my specific use case. This involves adding further files which should be mounted by some of the executed containers. One example would be an JSON-file with an extended vehicle model to by mounted by the Kuksa.Val databroker container.

Is there a way to include such files or the download of such files in the desired state configuration one can send to the VUM (https://eclipse-leda.github.io/leda/docs/device-provisioning/vehicle-update-manager/)?

Or is there another "Leda-way" to get such files to the Leda host-system without the need to build a new custom Leda image and apply it through the VUM and Self-Update-Agent?

The Leda documentation about building should contain a chapter about corporate environments, where it is required to set up a local GOPROXY container, so that Yocto Go-Recipes can be built properly.

A goproxy is a special GoLang specific proxy and is available as a Docker container.

@vasilvas99 did this setup already and may have more insights.