Skip to content
This repository has been archived by the owner on Feb 25, 2020. It is now read-only.

Suggestion: safe mode healing / fleet management #62

Open
chuank opened this issue Oct 30, 2015 · 2 comments
Open

Suggestion: safe mode healing / fleet management #62

chuank opened this issue Oct 30, 2015 · 2 comments

Comments

@chuank
Copy link

chuank commented Oct 30, 2015

Automatically handling system-part updates on spark-server will be awesome. Especially when firmware updates need to be updated en masse to a large number of devices on the local cloud.

Can there be a way to manage a local fleet of devices, giving administrators the ability to batch-update devices with new system-part firmware as well as user firmware? Right now it's a process that's done via particle-cli, one device at a time.

Perhaps there can a 'firmware' folder on spark-server where custom system-parts and user firmware can be uploaded to.

spark-server can then update information on each device's system+user firmware versions, and OTA what's different only to devices that need an update.

The [deviceid].json file stored for each claimed device in the core_keys folder seems an ideal place to track this additional information.

We can then serve a simple JS admin UI on the server to manage the files in the core_keys folder and effectively build our own fleet management console.

@KarbonDallas
Copy link
Contributor

@chuank safe mode healing and fleet management are things we've already implemented on our cloud! Fleet management will be out of beta shortly, and I suspect this is exactly what you're looking for.

@chuank
Copy link
Author

chuank commented Oct 31, 2015

@emilyrose when will we see these features trickle down to spark-server? Hope it won't become a massive operation making these features available for local clouds.

lbt pushed a commit to lbt/spark-server that referenced this issue Feb 28, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants