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.
Drew Moseley is a technical solutions architect at Northern.Tech, where he works on the Mender.io open source project to deploy OTA software updates to embedded Linux devices. Throughout his career, Drew has focused on embedded software and developer tools, including embedded Linux and Yocto. He has worked at Mentor Graphics, Red Hat, Intel, and Monta Vista Software on embedded projects such as RAID storage controllers, direct and network-attached storage devices, and graphical pagers. He spent the last seven years working in operating system professional services, where he helped customers develop production embedded Linux systems. Drew is a frequent speaker at conferences such as Embedded Systems Conference and All Systems Go. He was raised in Tampa, Florida, and attended the University of Florida.
©2018, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org