Vehicle Update Manager Configuration with Eclipse Kanto

[eriksven]

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?

[vasilvas99]

Hi, @eriksven yes your assumption that the last public release of VUM is expecting k8s as backend and we are still waiting for the OSS contribution for the updated version that uses Kanto-CM instead.

Currently your workflow of copying the ready-made manifests to /data/var/containers/manifests (with scp for example) and waiting a few seconds for the auto-deployment service to pick them up is the correct one.

[eriksven]

Thank you for the response, then I will wait for the updated VUM and stick to the scp and auto-deploy solution in the meantime.