| ID | device-lifecycle.ota-rollout |
|---|---|
| Description | Operator starts a staged campaign; edge agents download, apply and report firmware updates with health gates between stages. |
| Key | ota-rollout |
| Type | Sequence Workflow Diagram |
| Tags | firmware high |
Rolling out firmware is the highest-risk fleet operation: a bad build can brick devices at scale. This workflow makes rollout staged and reversible — a new version is released to a tiny cohort first, and only advances if health metrics stay green.
Staged by default
Default stages are 1% → 10% → 50% → 100%. Between stages the Progress Tracker evaluates a health gate; a regression auto-pauses the campaign.
| Number | Source | Destination | Description |
|---|---|---|---|
| 1 | Operator | Dashboard | Start rollout campaign |
| 2 | Dashboard | OTA service | Create campaign (version, cohort, stages) |
| - loop For each stage | |||
| 3 | OTA service | Edge agent | Offer update to stage cohort |
| 4 | Edge agent | Object storage | Download signed package |
| 5 | Edge agent | Device | Stage and apply |
| 6 | Device | Edge agent | Apply result |
| 7 | Edge agent | OTA service | Report progress |
| - if Health gate passed | |||
| 8 | OTA service | OTA service | Advance to next stage |
| else Failure rate too high | |||
| 9 | OTA service | Dashboard | Auto-pause for review |
| end | |||
| end | |||
| 10 | OTA service | Dashboard | Campaign metrics |
An operator defines the target version, the device cohort and the stage plan in the OTA Service.
Each stage offers the update to its cohort; agents download the signed package from object storage.
Devices stage, apply and reboot; the edge agent reports per-device success or failure.
If the cohort’s health is within bounds the campaign advances; otherwise it auto-pauses for operator review.