Skip to Content

Edge Devices

Adding Edge Devices

With additional edge devices (i.e., industrial PCs) you can deploy IronFlock apps to more machines and offload app operations from the appliance. The appliance itself already serves as an edge device, but you can attach more edge devices in the same way as you would deploy edge devices in the IronFlock cloud. Just go to Project Settings -> Devices -> New Device and follow the instructions.

The commands shown there are the same as in the cloud. The .flock file the appliance issues names the appliance’s download mirror as the agent’s update server, and ironflock agent install (release 2.1.0 and later) takes the device agent from that mirror; what the mirror does not hold, such as an agent for an architecture no device on the appliance runs yet, comes from the internet, with a warning. ironflock os install does the same for the IronFlockOS catalog, image and hardware list. See Devices of an IronFlock Appliance.

Some downloads of the installation still come from the internet: the install script and the ironflock command from ironflock.com, and the distribution’s packages and, where it is missing, Docker from their own servers. So set up a new device where it has internet access, directly or through a corporate proxy. When the appliance runs HTTPS with its own CA, the mirror works for the installation only where the device’s system trusts that CA. ironflock os flash and ironflock os install take that CA with --ca-cert, for their download and for the IronFlockOS they set up (0.17.0 and later). After the installation the device only needs to reach the appliance, which also serves its later updates (see Device Agent Updates).

Device Agent Updates

Edge devices attached to the appliance receive updates of the IronFlock device agent from the appliance itself — they never contact instance-registry.ironflock.com and need no internet access for it:

  • Plain (IP) mode: http://<appliance-host>:15002/dl — the same port devices already use for registry tokens.
  • Domain/TLS mode: https://registry.<appliance-domain>/dl on port 443.

The appliance keeps a local mirror of these updates and fills it from https://instance-registry.ironflock.com (already part of the firewall allowlist). It downloads only when an administrator starts a sync, and once by itself on a new appliance. On the appliance, go to Profile → Instance License and select Manage next to Device updates. From the IronFlock cloud, without logging in to the appliance, go to Profile → Instances and select the entry in the appliance’s Device updates column, or Device updates… in its menu. The Device updates dialog shows what the mirror holds and how much disk space it uses. Sync all or Sync now in a section starts a sync, and you can delete what you no longer need. What you delete stays deleted until the next sync.

For the device agent, the mirror holds the current release, for the operating systems and processor architectures of the devices registered on the appliance. A version is offered to devices only once it is completely present on the appliance; until then devices keep the previous one. The sync that completes a new version deletes the previous one. After you add the first device of an operating system or architecture that no other device on the appliance runs, start a sync so that this device gets agent updates too.

The agent downloads from the signed tree <base>/device-agent/ (a signed manifest-v2.json and the binaries with their .sig signatures), verifies every update before applying it and rolls back automatically if the new version does not come up. Updates are applied only when the agent starts or when a user starts the update in Studio.

A device learns the update location from its .flock file (update_url) and, from agent version 0.21.2 onward, also from the appliance on every heartbeat — so a changed appliance IP or a switch to domain mode propagates to the devices automatically.

Devices provisioned before this feature that still run an older agent need their .flock file re-downloaded once. On Windows: stop the service (& "$env:ProgramData\IronFlock\DeviceAgent\device-agent.exe" service stop), replace %ProgramData%\IronFlock\DeviceAgent\device.flock with the new file (saved without a BOM) — on devices installed before agent 1.4.0 the folder is %ProgramData%\IronFlock\Reagent — then start it again (& "$env:ProgramData\IronFlock\DeviceAgent\device-agent.exe" service start).

IronFlockOS and Firmware Updates

Devices running IronFlockOS get their operating-system updates from the appliance as well (device agent 1.6.3 and later). The mirror holds the update of the current IronFlockOS release for each OS image the appliance’s devices run, and deletes it once no device runs that image any more. Firmware updates offered to a device are held too (device agent 1.6.7 and later); a firmware file no device has asked for in 30 days is deleted. Both are synced in the same Device updates dialog. The mirror also holds IronFlockOS install images, but only those an admin of the appliance added to it: for each added image, the disk image and hardware list of the production release. ironflock os install takes them from there, so a machine that reaches the appliance but not the internet can be converted. An image that was not added is not downloaded on request: ironflock os install then takes it from the internet, with a warning, and fails when the machine cannot reach it (Where the Files Come From). Images for writing a drive are not mirrored: FlockFlasher and ironflock os flash download them from the internet, and the installer stick cannot be added to the mirror.

Last updated on