Introduction
This article describes how to update the Torizon for Maivin operating system using the official Au-Zone repositories. System updates are performed using OSTree. When using Torizon Cloud these updates can be managed through the centralized website, otherwise you will need to perform the updates manually on each system. For more advanced ostree usage refer to the ostree documentation.
Note: a similar article targeted at updating Torizon for Maivin built locally using Yocto is also available: Local Torizon Updates.
Torizon Cloud
Torizon for Maivin can also be managed through the Torizon Cloud dashboard. Contact info@au-zone.com to inquire about this functionality.
Requirements
- Maivin 1 or 2 with a connection to the internet.
- Torizon for Maivin version 6 or newer
- Refer to Maivin System Recovery if running on an older release, such as BSP5.
- SSH access to the Maivin
Repository
Note: this step is only required for Torizon for Maivin releases before 6.5.0.0. Newer releases have the repository pre-configured.
The OSTree repository configuration for Torizon for Maivin can be downloaded at the bottom of this article, for reference it is included below.
[remote "maivin"]
url=https://maivin.deepviewml.com/ostree
branches=torizon/maivin/release
This file should be installed into the following location.
/etc/ostree/remotes.d/maivin.conf
After which you can test the configuration by querying the remote.
$ ostree remote refs maivin
maivin:torizon/maivin/main
maivin:torizon/maivin/release
Which shows the main and release branch references. The release branch is the default branch which tracks official Torizon for Maivin releases.
The main branch provides pre-release updates which have not been as thoroughly tested but can be used when suggested by a support inquiry when testing a fix or new feature.
Updating
The update process is performed in two steps, first the latest artifacts are pulled from the ostree repository, next they are deployed to the Maivin platform. Use the ostree pull command to get the updates.
$ sudo ostree pull maivin
1 metadata, 0 content objects fetched; 255 B transferred in 0 seconds; 0 bytes content written
Then use the ostree deploy command deploy the new updates. Current updates will be in the "edgefirst" branch.
torizon@verdin-imx8mp-15139764:~$ sudo ostree admin deploy torizon/maivin/release
Copying /etc changes: 4 modified, 10 removed, 16 added
Transaction complete; bootconfig swap: yes; bootversion: boot.0.1, deployment count change: 0
Freed objects: 32.0?MB
The deployed update will be loaded on the next boot. If there is an error the system will restore the previous release after 4 failed boot attempts. The following demonstrates querying the status of the ostree deployment to see the currently booted version and the pending version which will be applied on the next boot.
$ ostree admin status
torizon 0e7c39e434513d383fb673a457b087cfe692b2ce7f931a3cd2781318c70d84ca.0 (pending)
Version: 6.5.0.2
origin refspec: torizon/maivin/release
* torizon 39c2682888a9bed9b6a64e0b4eb3ef8749f9828e9e105a3b5fb44fba5df286a6.0
Version: 6.5.0.0
origin refspec: torizon/maivin/release
After a reboot you may also confirm the currently installed release by reading the /etc/os-release file.
$ cat /etc/os-release
ID=torizon-maivin
NAME="Torizon for Maivin"
VERSION="6.5.0.2+build.1 (kirkstone)"
VERSION_ID=6.5.0.2-build.1
PRETTY_NAME="Torizon for Maivin 6.5.0.2+build.1 (kirkstone)"
DISTRO_CODENAME="kirkstone"
BUILD_ID="1"
ANSI_COLOR="1;34"
VARIANT="Maivin"
Changelogs
The release change logs are available from ostree, note this only include the comments on ostree updates and not the full system changelog.
$ ostree log torizon/maivin/release
commit 0e7c39e434513d383fb673a457b087cfe692b2ce7f931a3cd2781318c70d84ca
Parent: 39c2682888a9bed9b6a64e0b4eb3ef8749f9828e9e105a3b5fb44fba5df286a6
ContentChecksum: 64484116a7cf979e602b95eb9ec34eba27a453929c3767fba2b90200a847a0bf
Date: 2024-03-18 19:46:33 +0000
Version: 6.5.0.2
Fixed Docker-related system regression (broken user accounts).
Change-Id: I26b2be5ce8afd4d48fa26beab728abe3cadaa5b9
<< History beyond this commit not fetched >>
Comments
0 comments
Please sign in to leave a comment.