I was able to move a device from my openBalena deployment to balenaCloud and back using the following steps:
- Log in to balenaCloud
- Create a new fleet
- Add Device > Download configuration file > new-config.json
- ssh into device
- copy /mnt/boot/config.json > old-config.json (save this for later)
- os-config join ‘json from new-config.json’
- Select device in new fleet when it appears
- Open Terminal to Host OS
- os-config join ‘json from old-config.json’
I am also able to move a device from openBalena to balenaCloud and update balenaOS on the device.
However, I did not try to move the updated device back to my openBalena 2.x.x deployment since it does not support newer versions of balenaOS.
This is the next thing I will test:
- Setup new openBalena 2.x.x
- Add a device with balenaOS 2.48.0+rev1
- Upgrade to openBalena 3.x.x
- Move device to balenaCloud
- Update device to latest balenaOS
- Move device back to openBalena
This seems like it may be a viable upgrade path if there are no other options. However it would be awfully slow since I have a number of devices to upgrade.
If/when the remote host update feature comes to openBalena, will I be able to update my balenaOS 2.48.0 devices that way, or will they need to be updated to a newer version of balenaOS before they can receive remote OS updates?