AUTOSAR vucm

vucm — Vehicle Update and Configuration Management

← back to AUTOSAR

What ARA defines

ara::vucm is the fleet/vehicle-level counterpart to UCM: campaign management, rollout policies, dependency resolution, and approval workflows that orchestrate updates across many ECUs/vehicles. Where UCM is "update this machine," VUCM is "roll out this version to this group, in phases, with sign-off."

Our adaptation

Theia's vucm is the fleet-side OTA + provisioning surface, realized as two controller-side tools rather than an on-device FC:

• Mender server = the OTA transport + campaign engine: deployment groups, phased rollout, status. We drive it with deploy/vucm/fleet.py — a thin Mender Management-API client (upload a theia-release artifact → deploy to a device group → track), the reusable spine a real management server builds on. A full server→rig OTA loop (deployment → pull → theia-release module → UCM hand-off) is live-verified.
• Ansible controller = the provisioning campaign surface (agentless SSH push; no on-rig convergence agent), pairing a Mender deployment group with an Ansible inventory group as the two fleet handles.
• deploy/vucm/campaign.sh drives one update to the on-device UCM directly (the self-hosted demo path) via the artheia probe — the same RequestUpdate a Mender state-script triggers in production.

We keep ARA's "fleet campaign vs. device agent" split exactly; we just realize the fleet side with off-the-shelf Mender + Ansible instead of a bespoke VUCM stack — deliberately pragmatic, and not a certified VUCM.