Confirmed users
1,905
edits
Auto-tools/Projects/Lifeguard: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(→Goals) |
No edit summary |
||
| Line 6: | Line 6: | ||
Lifeguard will not be responsible for flashing or installing builds on target devices. | Lifeguard will not be responsible for flashing or installing builds on target devices. | ||
= Design = | |||
TBD, but [https://github.com/mozilla/autophone Autophone] provides some of this already, so probably is a good place to start. | |||
= Requirements = | |||
# Lifeguard should provide a mechanism for devices to register themselves with it. | |||
# Once a device is registered with Lifeguard, it should periodically poll the device to verify that it's still alive. | |||
## If the polling fails, Lifeguard should attempt to recover the device by resetting its power up to N times. | |||
## If resetting the device fails, Lifeguard should mark the device as 'offline'. | |||
# Lifeguard should provide a web UI that users can use to see and change the status of connected devices. | |||
## The UI should allow users to set the status of the device (offline or online) and to attempt rebooting or resetting its power. | |||
## If a user marks a device as online, Lifeguard should attempt to bring the device online; if it fails, it should return the status to offline. | |||
# Lifeguard should provide an API with which remote components can interact with it. | |||
## | |||