Upgrade to 8.0 [ Mandatory ]
This guide outlines the process for upgrading your ThingsHub installation to version 8.0
Following the Upgrade Path
For a seamless upgrade, consult the Upgrade thingsHub document to determine the exact sequence required for your current version. Look for "mandatory" in the page title to identify essential steps in the upgrade path. These mandatory upgrades ensure compatibility and prepare your system for the final upgrade to 8.0.x.
What's New?
Before upgrading, be sure to do the following:
Review the What's New page for details on new features and functionalities introduced in version 8.0.x. Additionally, the Breaking Changes page highlights any significant changes that might impact your existing setup.
The Action Required Section will guide you through the essential migrations that need to be done before the upgrade to thingsHub 8.
Upgrading from Previous Versions
Direct upgrades to thingsHub 8.0 can be done if you are using any thingsHub version 7.5.latest+.
If you're using an older version, an upgrade to version 7.5.latest is recommended before you upgrade to thingsHub 8.0.x.
Before You Begin
Make sure to read the What's New for the release 8.0.x.
Check out the Breaking Changes page to see if this version has any major breaking changes.
Make sure the thingsHub Installation to be upgraded is in version 7.5.latest.
Determine which version to upgrade to
This section shows how you can list all the available patch versions available for this thingsHub version i.e. 8.0. You can select the patch version you want to upgrade your thingsHub Installation to. We recommend using the latest available patch version to not miss out on any bug fixes and security patches.
#!/bin/bash
helm3 repo add smartmakers http://helm.smartmakers.de
helm3 repo update
helm3 search repo smartmakers/th-tenant --version 8.0 --versions
Update Tenant Configuration
This section outlines all the changes that you need to make and that are available in the tenant configuration file. These changes encompass incremental changes required from thingsHub 7.5.x.
For thingsHub 8.0, no tenant configuration changes are required. Your existing tenant configuration from version 7.5.x will continue to work without modifications.
Backup Databases
Before applying the upgrade, back up all your data from both the time-series database and the relational database. This section explains how you can backup and restore your databases.
Postgres
#!/bin/bash
# backup:
pg_dump -U <your-user> -h <address-to-your-db> -p <port> --database <your-database> --no-owner --format=t --verbose >sql.dmp
# restore:
pg_restore -d <database> -h <address-to-your-db> -p <port> -U <your-user> --no-owner --role=<your-user> sql.dmpInfluxDB
Make sure that InfluxDB is port-forwarded to port 8086 in the system where you're running the shell commands.
#!/bin/bash
# backup:
influxd backup -portable -db things_hub ./influxdata/
# restore:
influxd restore -portable -db things_hub ./influxdata/If you have set up any other backing-up mechanisms in your infrastructure, you can leverage that as well for the backups in place of the one mentioned above.
Apply the Upgrade
After setting up everything, we can proceed to upgrade the thingsHub Installation.
#!/bin/bash
helm3 repo update
helm3 upgrade <your-thingshub-installation> --namespace <your-thingshub-namespace> smartmakers/th-tenant --version 8.0.0 -f <tenant_configuration.yaml> --atomicPost Upgrade Steps
Post Upgrade Testing
We recommend doing smoke testing on your thingsHub Installation after the upgrade to ensure that the system is functioning smoothly.
Since the Device Management functionality has also seen a major overhaul with thingsHub 8, with the introduction of Device Keys, and the migration of all device identifiers to a central Key Store.
We recommend testing/verifying the functionality of registering/deregistering different classes of devices to/from their respective Network Servers, and seeing that the device keys for your LoRaWAN devices are properly populated as part of your upgrade to ThingsHub 8.0.
Device Keys can be viewed in the Network tab of the Device Detail page.
Device keys for non-LoRaWAN devices will only be populated after the device receives one uplink after the upgrade.