Setting Up Your Edge Computing Gateway

Setting Up Your Edge Computing Gateway

The four routes

Not alternatives so much as tools for different jobs.

Golden image
The complete software state. For any fleet you want built identically.
Configuration file
Settings only. For devices that already run the right software.
By hand, or by script
Whatever you install. For a handful of devices, and the reference unit.
Remote management (RCMS)
None of your software. Manages Robustel firmware, apps and settings afterwards.

Getting a device from its box into production means putting your software, your settings and your credentials onto it. RobustOS Pro gives you four ways to do that. They are not alternatives to one another so much as tools for different jobs, and most deployments use two or three together.

The four routes

RouteWhat it puts on the deviceBest for
Golden image (clone package)The device's complete software state — your settings, packages, apps, containers and data, plus the Robustel system software on the reference unitAny fleet you want built identically
Configuration fileSettings onlyDevices that already run the right software but need different settings
By hand, or by scriptWhatever you installA handful of devices — and building the reference unit for a golden image
Remote management (RCMS)None of your software — it manages Robustel firmware, Robustel-built apps and device settings afterwardsAny deployment you will manage remotely

1 · Golden image

Set one device up, take a clone package off it, put that package on every other device.

Build the reference unit
Then create the package on the command line.
→
Clone package
Your software and settings plus the Robustel system software.
→
Onto the fleet
Pre-installed at the factory, or per device by USB.
Becomes the factory baseline
A reset returns to your image, credentials included.
Shared identity
Decide which credentials must be unique; issue them after restore.
Exact hardware match
Same model and hardware variant, memory included.

Set one device up exactly as you want it, take a clone package off it, and put that package on every other device. The package holds the device's complete software state — your configuration, the packages and apps you installed, container images and data, and your user data, together with the Robustel system software (the Linux kernel included) that was on the reference device. Restoring it replaces the whole of the target device's software, so every unit built from the package ends up on the same Robustel software version as the reference device — even if it left the factory on a different one, or has been updated since.

Building the package. Creation is a command-line step (rbt-system-mgmt clone create) — there is no button for it in the web interface. Before you build: clear the package cache (apt-get clean), make sure the writable layer has at least 50% free space, and use an ext4-formatted USB stick. Check the finished package with rbt-system-mgmt clone info before you rely on it.

Getting it onto the fleet — two routes:

  • Factory pre-installation. Send the package to Robustel Technical Support and it can be installed during manufacturing, so devices arrive already carrying your build. This is the practical route at volume.
  • Per device, by USB. Restore the package on each unit yourself. Fine for tens of devices; slow for hundreds.

Step-by-step instructions are published in the Robustel knowledge base: How to Bulk Copy EG Device Configurations & Applications.

Three things to know before you commit to this route:

  • The image becomes the factory baseline. Once a clone is installed, a factory reset returns the device to your image, not to a clean out-of-the-box state. That is usually what you want — but it also means a reset restores whatever credentials the image carries rather than clearing them.
  • Every unit shares the image's identity material — SSH host keys, TLS certificates, VPN credentials and cloud identifiers. Decide which of those must be unique per device and issue them as a step after restore. See Securing Your Device.
  • The hardware must match exactly — same model and same hardware variant, memory configuration included. A package built on a unit with 2 GB of RAM will not restore onto the same model fitted with 1 GB.

2 · Configuration file

Settings without the software. Export from one device, import on another through the web interface.

Settings only
Not packages, apps, containers or data.
Applies on reboot
The device restarts to use it.
Check after importing
An unreadable file leaves the device on its default configuration.

If your devices already run the software you want and differ only in how they are configured, you can export the configuration from one device and import it to another through the web interface. This is a super-admin operation.

  • It carries settings only — not installed packages, not apps, not containers, not data. If the target device does not already have the software, the settings alone will not put it there.
  • It applies on reboot. The device restarts to take the imported configuration into use.
  • Check the device after importing. If the file cannot be read, the device comes up on its default configuration rather than yours — so confirm the settings landed before you consider the device provisioned, and keep a known-good copy of the file.

Useful for per-site variation on top of a common build: one golden image everywhere, then the site's own configuration file on each.

3 · By hand, or by script

Your side is a Debian machine: SSH, sudo and apt. Anything you can script, you can provision.

This is also how you build the reference unit for route 1. A scripted build feeding a golden image scales very well.

A RobustOS Pro device is a Debian system, and your side of it behaves like any Debian machine: you can reach it over SSH, use sudo, and install software with apt — so anything you can script, you can provision. Between your software and the Debian base sits Robustel's own system software, the Linux kernel included; that part is Robustel's to replace through firmware releases (see What an Update Changes).

  • Containers: the Docker command line is not pre-installed. Docker works alongside the device firewall: decide which container ports may be reached from outside, and block the rest with Custom Rules (Network → Firewall).
  • This is also how you build the reference unit for route 1. Whatever you install and configure here is what the golden image captures.

Sensible for a handful of devices, for pilots, and for teams who already provision Linux estates with their own tooling. It does not scale on its own — but a scripted build feeding a golden image scales very well.

4 · Enrolling in remote management

How you operate devices after deployment, alongside whichever route you use.

Manages
Firmware updates, Robustel-built apps, device configuration.
Robustel software and settings
Does not carry
Your Debian packages or containers. Full-image installs stay on site.
Your own software
Can arrive already in your account. Robustel can pre-register your devices at the factory; with RCMS switched on there, each one appears in your account the first time it starts. You can also add a device yourself, by its serial number.
Otherwise it ships switched off, and a default-configuration restore switches it off again. Check it before you call a device done.

RCMS is how you operate devices after they are deployed rather than how you first set them up. For a 2.4.x fleet it manages Robustel's software and your device settings: firmware updates, distribution of Robustel-built apps, and device configuration.

What it does not do is put your own software on a device. Debian packages you install, and containers you run, have no RCMS delivery path on 2.4.x. Full-image installation is not an RCMS operation either; that stays a physical, on-site task.

  • Robustel can pre-register your devices to your RCMS account. At the factory, Robustel can add the devices to your account by serial number and IMEI or MAC address. With RCMS switched on at the factory, each device appears in your account the first time it starts, with no setup on your side. You can also add a device to your own account yourself, by its serial number.
  • A device's cloud identity comes from its serial number. That means an enrolled device re-registers itself after a factory reset or a re-image — a recovered device comes back into your fleet on its own.
  • Otherwise it ships switched off, and restoring the default configuration switches it off again. If your provisioning sequence ends with a configuration restore, check that remote management is still enabled before you call the device done.
  • Which operations are available depends on your RCMS plan.
Worth being clear about
Enrolment is not an alternative to routes 1–3 — it sits alongside whichever one you use.

Choosing your route

If you haveUse
More than a handful of identical devicesGolden image, pre-installed at the factory if the volume justifies it
Same software, different settings per siteGolden image for the build, configuration file for the site
A few devices, a pilot, the reference unitBy hand or by script
Any deployment you will not revisitEnrol in remote management as well
  • More than a handful of identical devices → golden image, pre-installed at the factory if the volume justifies it.
  • Same software everywhere, different settings per site → golden image for the build, configuration file for the site.
  • A few devices, a pilot, or building the reference unit → by hand or by script.
  • Any deployment you will not physically revisit → enrol in remote management as well.

Who updates what, in service

Decide this before you deploy. RCMS covers Robustel software and settings, not software you installed.

LayerWho and how
Firmware, kernel, Robustel appsRobustel publishes; you install, per device or from RCMS
Device settingsYou: web interface, command line or RCMS
Your packages, applications, containers, dataYou, over SSH with apt
A golden image builds a fleet; it does not update one. Plan your own route: your signed repository, driven over SSH.

Provisioning puts software on a device. Keeping it current afterwards divides along a line worth understanding before you deploy, not after.

LayerWho updates itHow
RobustOS Pro firmware, the Linux kernel, Robustel's own applicationsRobustelWe publish releases; you install them — per device, or across a fleet from RCMS
Device settingsYouWeb interface, command line, or RCMS
Your own Debian packages, your applications, your containers, your dataYouThe device is a Debian 11 machine — you reach it over SSH and use apt

RCMS covers the first two rows. It is not a delivery channel for software you wrote or installed yourself.

A golden image builds a fleet; it does not update one
Restoring a clone replaces a device's whole software state and is a per-device operation — it is how you get devices into service, not how you ship your next release to devices already in the field.

So plan your own update route before you deploy. On a fleet you cannot physically revisit, the practical shape is the one you would use for any Debian estate: publish your packages to your own signed repository, point the devices at it, and run the upgrade with the tooling you already use over SSH. See Updating Your Device → Shipping a new version of your own software.

Four decisions before you provision

Whatever state the reference unit is in propagates to the fleet.

1
Factory baseline
Stays clean, or becomes your image?
2
Unique credentials
Which ones, per device?
3
Automatic USB updates
On or off in your image?
4
Remote management
Enabled in your image?
1
Does your factory baseline stay clean, or become your image?
Choosing a golden image changes what every future factory reset on those units returns to.
2
Which credentials must be unique per device?
Decide before you build the image, not after the fleet is deployed.
3
Are automatic USB updates on or off in your image?
It ships off — but the image carries your configuration, so if you switch it on while building the reference unit, every device built from that image has it on too.
4
Is remote management enabled in your image?
Same principle — whatever state the reference unit is in propagates to the fleet.
Decisions 3 and 4 are the ones most often noticed after deployment rather than before — see Securing Your Device.
What an Update Changes
What updates and resets do to a provisioned device.
Securing Your Device
Hardening a device once it is set up.
Updating Your Device
Updating devices already in service.

What this guide does not cover

Next · step 5 of 13Securing your device →The hardening checklist for putting a device into production.