Resin.io Seattle Workshop and Hackathon 2017-05-13

13

Transcript of Resin.io Seattle Workshop and Hackathon 2017-05-13

SOFTWARE FOR DEVICES IS A NIGHTMARE

“The Web brought about the end of the annual software release cycle...The industrial internet will bring about a similar change in the physical world.”- O’Reilly, “Industrial Internet”

WE LIVED THE PROBLEM

RESIN.IO DELIVERY PIPELINE

Tailored for containersContainers will revolutionize

connected devices, and resinOS is the best way to run them

Just the essentialsA minimal Linux with the services

needed to run Docker reliably on an embedded device - nothing else

Easy to portBased on Yocto Linux for easy porting to most capable device types across

varied CPU architectures

ON-DEVICE S/W ARCHITECTUREAPPLICATION CONTAINERs

User Application

Language Packages

Language Runtime

OS Packages

Base Image

RESIN.IO CONTAINER

Resin Agent

Language Packages

Language Runtime

OS Packages

Base Image

Application Containers run a full stack in isolation: code, runtime, system tools, system libraries etc.

Most updates with resin.io are at the application container level. When you “git push” code to resin, it is an application container that is deployed.

Deployment, management, and monitoring tasks are performed by the Resin Agent. The Resin Agent is fully open source.

ResinOS is a lightweight container-enabled host operating system. It is also fully open source.

Because it is so minimal, updates to ResinOS are very infrequent. They are performed with ResinHUP.

#BLOG4SWAG

RESIN.IO FLEET MANAGEMENT

RESIN.IO DEPLOY LOGS

RESIN.IO DEVICE VISIBILITY

RESIN.IO DEVELOPMENT

RESIN.IO - FULL STACK UPDATES

extension container(s)resin.io container application container

APPLICATION UPDATES

(CONTAINERS)

HOST OS UPDATES

(RESIN HUP)

Let’s Get Started

Signup: dashboard.resin.io

Docs: docs.resin.io