Confirmed users
1,905
edits
Auto-tools/Projects/Lifeguard: Difference between revisions
Jump to navigation
Jump to search
→Requirements
| Line 24: | Line 24: | ||
## an API to return a checked_out device to the pool. This API should accept a device identifier. After being returned to the pool, Lifeguard should reboot the device and verify it is alive, after which the status should be updated to online. | ## an API to return a checked_out device to the pool. This API should accept a device identifier. After being returned to the pool, Lifeguard should reboot the device and verify it is alive, after which the status should be updated to online. | ||
## additional APIs needed to support the Web UI above | ## additional APIs needed to support the Web UI above | ||
# Lifeguard should scale to handle a large number of devices (several hundred, still TBD) | |||
# Lifeguard should have unit tests, that we can run before changes. | |||
# Lifeguard should have a staging environment, and integration test that we can run in a live environment. | |||
# Lifeguard should maintain a detailed log including, among other things, details on device registrations, device state transitions, and all API requests. | |||