Upgrading

Since TrinityX sees new features on regular basis, there is a need to upgrade to more recent versions. Within a release, key components can be upgraded.

for example: TrinityX 14, allows for upgrading to 14.1, 14.2 ... 14.4

Release 15

TrinityX release 15 is significantly different compared to release 14. We are currently looking into an upgrade path from 14.x to 15.

Using the cloned TrinityX branch

Upgrading relies on having the original cloned TrinityX repo on your local controller. If this one is no longer present, a fresh clone can be used and group_vars/all.yml file and hosts files can be configured. Also see installation steps. There would NOT be a need to rerun prepare.sh or the entire playbook(s). After the configuration of the required files, the next steps can be followed.

BIG NOTE: make sure to use the correct release to pull or clone. The main branch on github is always the latest. It is possible to clone using an older release by selecting it first:

Other options are to download the tarred or zipped releases:

The actual upgrading steps

There are two main streams of upgrading. The ansible part, which contains mainly fixes for configuration of the the controller and images. The other stream are the components like OnDemand apps (puns), Luna and others. In some cases both streams have to be upgraded in tandem.

Ansible upgrade, or a pull

To upgrade to the latest ansible code, simply pull into your existing TrinityX cloned repo. Make sure to pull from the correct release. The next step is important, which is verifying the differences between your existing group_vars/all.yml and group_vars/all.yml.example to work out possible differences. Think of keys or settings that were added since your last installation. The best approach would be to rename group_vars/all.yml, copy group_vars/all.yml.example to group_vars/all.yml and change the new all.yml according to your original (renamed) all.yml.

TrinityX components

Since all components are set up through the ansible code are sourced from other repositories or locations, these components can be upgraded without any change or alterations to the ansible code. In short, in most cases no new pull is required. The list below shows tested procedures for upgrading key components. If the component you're looking for is not in the list, please reach out to us.

Luna:

ansible-playbook controller.yml --tags=luna

ood-apps release 14.x:

ansible-playbook controller.yml --tags=ood-interactive-apps

ood-apps release 15:

ansible-playbook controller.yml --tags=ood-apps

monitoring:

ansible-playbook controller.yml [<other>.yml] --tags=monitoring

The optional <other>.yml refers to compute-default.yml or any other used compute yml file. This could include k3s-default.yml. This differs per site and choice. What was run before, as in which playbooks where used during the initial installation, have to be included again.

Please note that any of these upgrades might (most likely) overwrite customizations as per installation notes. It's recommended to keep copies of your customizations and place these back or merge after the upgrade.