Key requirements for software updates for the IoT
A key requirement for connected Linux devices is the ability to deploy remote software updates to them so that bugs, vulnerabilities, and new features can be addressed. Drew Moseley shares best practices and the current state of software updates for connected devices, drawn from interviews with more than 100 embedded developers undertaken as part of the Mender.io project.
| Talk Title | Key requirements for software updates for the IoT |
| Speakers | Drew Moseley (Mender.io) |
| Conference | O’Reilly Open Source Convention |
| Conf Tag | Put open source to work |
| Location | Portland, Oregon |
| Date | July 16-19, 2018 |
| URL | Talk Page |
| Slides | Talk Slides |
| Video | |
A key requirement for connected devices is the ability to deploy remote software updates to them so that bugs, vulnerabilities, and new features can be addressed while devices live in the field for up to 10 years. The process for enabling these updates must be: In order to address these requirements, design trade-offs must be made. Drew Moseley shares best practices and the current state of software updates for connected devices, drawn from interviews with more than 100 embedded developers undertaken as part of the Mender.io project. Join Drew to learn the most common update strategies, such as using A/B dual rootfs, maintenance-mode updates, package managers, and tarballs, and explore the trade-offs of each approach. Drew also details other important design aspects of an updater, such as validating deployment compatibility, integrity, authenticity, sanity checking after the update, handling update failures, identifying extension points, device portability, persistent user data, and reducing bandwidth consumption and downtime.
