Skip to content
JelinaJelina DocumentationTechnical documentation
Back to website

Cloud application deployment and OTA

A cloud Release is only the starting point; what matters is how devices safely receive and execute updates. This page explains the complete JelinaOS workflow from the device’s perspective, distinguishing it from ordinary remote software installation.

Device-side update workflow

Section titled “Device-side update workflow”
Publish a new version in the cloud
       │
       ▼
Agent synchronizes target state ──▶ Local confirmation (optional) ──▶ Download and verify
       │                                                                    │
       │                                                                    ▼
       │                                                        Write standby partition (A/B)
       │                                                                    ▼
       │                                                        Reboot and switch ──▶ Boot verification
       │                                                                                     │
       │                                                                       ✅ Pass: run new version
       │                                                                       ❌ Fail: roll back automatically
       ▼
Report update status to cloud in real time

Target state synchronization

Section titled “Target state synchronization”

The device agent periodically synchronizes the cloud target state, including application versions, system versions, and configuration, and applies detected changes according to policy. Devices need no public Internet ports; all communication uses secure channels initiated by the device.

Local confirmation (optional)

Section titled “Local confirmation (optional)”

For critical sites, updates can wait for on-site confirmation after reaching the device:

  • New versions are stored on the device first and do not execute immediately.
  • Installation starts only after on-site personnel confirm.
  • Confirmation status can be queried using device-side commands.

A/B switching and automatic rollback

Section titled “A/B switching and automatic rollback”
  • Updates write to the inactive partition while the current system continues running without interrupting business operations.
  • If boot validation fails after switching, the device automatically reverts to the original version.
  • If problems arise with an applied version, it can be rolled back at any time.

Offline updates

Section titled “Offline updates”

Devices without network access can use offline update packages: download packages, then apply them on site. This covers system, kernel, device agent, and application updates.

Incremental updates

Section titled “Incremental updates”

Sites with limited bandwidth can use incremental updates to transfer only differences between versions, significantly reducing downloads. Once an incremental package is specified in the cloud, the device installs it automatically.

Update targets

Section titled “Update targets”

The four update categories—system, kernel, device agent, and application/incremental packages—use the workflow above. For specific operations, see system updates.

Cloud operations

Section titled “Cloud operations”

Cloud release operations, including creating Releases, deploying to fleets or devices, staged rollouts, and rollback, are performed in JelinaCloud:

Section titled “Related documentation”