Managing your vehicle software with Eclipse Kanto and Eclipse Leda
summary
Eclipse Kanto provides a lightweight, Go-based device stack that runs Eclipse Kanto update manager plus standalone services, uses containerd for runtime and MQTT for cloud connectivity, and accepts a JSON “desired state” to drive updates. Eclipse Leda supplies a Yocto-based Linux image and uses Rauc with A/B partitions for OS flashing; Kanto’s container update agent downloads artifacts, applies updates, reports per-agent progress, and rolls back on failure. Demo shows successful and failed container updates; update manager and agent are near release.
AI-written summary · about
chapters (16)
- 0:00Eclipse Kanto & Leda intro
- 1:52Vehicle software challenges
- 3:58Software-defined vehicle reqs
- 4:41Eclipse Leda overview
- 6:10Eclipse Kanto overview
- 8:41Kanto architecture & features
- 10:07Kanto Update Manager concept
- 13:02Update workflow & roles
- 14:50Update agents roles
- 16:59Self-update agent OS
- 19:51Custom update agents
- 20:19Demo setup overview
- 21:25Live update demo
- 23:38Future plans for Kanto & Leda
- 25:05Next steps & features
- 26:10Q&A
related talks
32mAn Eclipse Automotive Stack for rapid-prototyping Software Defined Vehicles
47mFrom "Can't" to "Can" with Kanto
01h 02mEclipse IoT: State of the Union
25mEclipse hawkBit: Software Updates For The IoT
38mHow to Tame My Edge Devices?
34mAutomotive meets IoT: innovating your future vehicle
29mWhy Eclipse Kura and Eclipse Kapua treat EdgeOps headaches better than ibuprofen?
27mIntroducing Eclipse Hara