Deployment and operation
Deliver the application as a repeatable configuration: artifact, host software, device drivers, calibration and service settings have one recorded release identity.
Delivery forms
| Artifact | Application |
|---|---|
| Native package | A service installed on a managed PC |
| OCI container | A reproducible application environment with explicit device access |
| System image | OS, drivers and services delivered together for an embedded host |
An embedded image can use Yocto. Record the target board, OS / image, driver and SDK versions alongside the application and calibration; preserve that combination for recovery.
Startup, operation and recovery
- InstallPackage · version · configuration
- StartServices · readiness
- ObserveState · logs · resource load
- Update / recoverVersion change · restart
| Step | Operational behavior |
|---|---|
| Install | Verify artifact identity; apply host, device and network configuration |
| Start | Bring up drivers and capture first; start consumers when required inputs are ready |
| Monitor | Track process health, connection state, observation freshness, faults and storage |
| Update / recover | Apply a recorded release; restore the compatible artifact and configuration on failure; recheck readiness before resuming |
Example: x86 application and Jetson capture
The Jetson captures GMSL2 cameras and publishes timestamped observations. The x86 service consumes the same schema and calibration identity, runs task logic and connects to Control. Each host starts independently and reports readiness; the application pauses on stale input or lost connectivity.
Keep startup, health checks and recovery steps with the release. Use software integration for process ownership and commissioning for the installation's acceptance record.