-
Notifications
You must be signed in to change notification settings - Fork 0
Home
ibnHatab edited this page Jul 4, 2026
·
2 revisions
The cloud Ground Station for a Theia fleet — the operator-facing surface for day-2 fleet operations: enroll devices, plan and push software campaigns, watch rollouts, and aggregate device health. It augments a Mender OTA backend with a web UI and a small API.

Cloud / operator
│
Ground Station ← web UI + API (this repo)
┌─────────┴──────────┐
Mender GW fleet ops enroll
│ │ │
└── Mender Mgmt API + device pull ──┐
▼
colony (provision / orchestrate) ──runtime──► fleet rigs (theia)
on-device: VUCM ← UCM ← EXEC
Two planes, two authorities behind one surface:
| Plane | Ships | Authority |
|---|---|---|
| Base / runtime | supervisor + platform services | colony (SSH/Ansible) |
| App / SWP | the user's Functional Clusters (overlay) | Mender (OTA) |
The GS is a separate concern from the on-device product by design: fleet
tooling is a swappable adapter. Its only coupling to theia is the .mender
artifact contract the on-device theia-release update module consumes.
- Operator Guide — the full deploy workflow: bring up a rig, enrol it, create a Distribution, deploy, and watch the Action History.
- Setup — stand up the Mender GW + the GS containers.
The left nav is the whole operator loop:
- Deployment — the deploy board (pick a Distribution → fan out to boards).
- Fleet — enrolled devices, base runtime, app SWP, health.
-
Releases — the S3 runtime plane (what
theia releasepushed). -
Distributions — deployable app SWPs (what
theia release-swppushed). - Rollouts — Mender / on-device transport state.
See the Operator Guide for the step-by-step.
- Theia wiki — the framework, and the full Tutorial (ch. 6 is the hands-on GS deploy).
- colony — the provision/orchestrate adapter the GS drives for the base plane.