How continuous deployment is done on devices ( RaspberyyPi)


#1

I am working on the project where we have our application is running on raspberryPi 3 at remote application. Application upload video and audio files automatically and do the people counting at real time.

We want to use Resin.io for continuous deployment on these RaspberryPi devices for the updates. Now I have few questions

  1. Do we need static IP on raspberry pi for the continuous deployment ? Whether the updates will be pushed or pulled on the device ?

  2. What level of QOS we can get on resin.io ?


#2

Sounds like a cool project! Are you doing the counting/analysis on the Raspberry Pis and sending the data from there to the cloud or similar?

To answer your questions:

Do we need static IP on raspberry pi for the continuous deployment ? Whether the updates will be pushed or pulled on the device ?

No, you don’t need a static IP on the devices to use Resin. The devices will connect outbound to resin.io and poll for updates. Because this is a pull rather than a push, they can be behind a firewall, NATed, etc. and everything will continue to work.

What level of QOS we can get on resin.io ?

That depends a bit on what you mean. As far as the service goes, we do everything we can to ensure that resin.io stays up as close to 100% of the time as possible. We have a page you can follow the status of Resin and subscribe to service updates here: http://status.resin.io/

If you’re asking about something like Service Level Agreements (SLAs) on support, we can provide that as well. Those vary depending on the level of support you need for your application, the number of devices, and so forth. We’d be happy to chat with you directly about support SLAs! The best thing to do is to email us at hello@resin.io or visit our contact page and let us know the best way to contact you.