Fleet management and remote maintenance
After registration with JelinaCloud, devices join a unified cloud management system. A Fleet groups devices for management: joining a fleet automatically gives a device the following capabilities, without configuring each device separately.
Device-side capabilities
Section titled “Device-side capabilities”Continuous status reporting
Section titled “Continuous status reporting”The device agent continuously reports system version, network addresses, resource usage, operating temperature, and application and service status. The cloud device dashboard presents this information in real time, providing visibility without logging in to devices.
Automatic runtime policy execution
Section titled “Automatic runtime policy execution”The device agent automatically applies cloud-delivered runtime policies covering device behavior:
| Policy | Device behavior |
|---|---|
| Update trigger | Executes a new version immediately on arrival or waits for on-site confirmation |
| Production mode | Accepts only cloud access; direct LAN access is unavailable |
| Secure channel | Establishes an encrypted cloud connection for remote maintenance |
| Log reporting | Reports device logs to the cloud for retention according to policy |
| Write rate limit | Limits write speed during update installation |
| Alert thresholds | Reports temperature, memory, storage, or CPU threshold violations for cloud notification |
Policy changes synchronize and take effect automatically without a restart or manual intervention.
Batch update execution
Section titled “Batch update execution”When the cloud pins a system, kernel, or device agent version for a fleet, devices apply updates automatically:
- Updates follow dependencies, updating the system before the kernel/agent to maintain compatibility.
- A/B systems provide automatic rollback on failed updates without taking devices offline.
- Individual devices can pin their own versions independently of fleet policy.
- Devices without network access support on-site application of offline update packages.
Remote maintenance channels
Section titled “Remote maintenance channels”Devices provide remote maintenance through built-in secure channels:
- Remote SSH, remote desktop, and service operations.
- Remote shutdown and restart.
- Device service proxying: access services on devices through cloud forwarding.
Cloud operations
Section titled “Cloud operations”Fleet and device operations—creating fleets, adding devices, configuring policies, specifying versions, and granting access—are performed in JelinaCloud:
Common questions
Section titled “Common questions”Does a device need to restart after a policy change? No. The device agent synchronizes policies automatically and applies them immediately.
Can a device operate outside fleet management? Yes. Devices support local management and standalone modes; local capabilities remain fully available without the cloud.
Is remote maintenance secure? In production mode, devices are accessible only through the cloud. All maintenance operations use encrypted channels, and direct LAN access is unavailable.
Related documentation
Section titled “Related documentation”- Device registration and connectivity — How devices join the cloud
- Jelinvisor device agent — The device-side executor
- Networking and security — Secure channels and access control