TradeSense Upgrade

TradeSense upgrade are performed via the TSS thanks to "upgrade bundles".

Once deployed on the TSS under the appropriate section and associated to a specific TradeSense cluster, upgrades occur automatically.

Terminology

On the TSS, upgrade bundles are referred to as "BT Productivity Tools Firmware".

TradeSense upgrade bundle,  BT Productivity Tools Firmware, BTPT bundle are all synonyms.

TradeSense 1.1 VA upgrade bundle version

TradeSense 1.1 VA comes with the upgrade bundle 9.3.4 pre-installed. It must be updated to the latest available upgrade bundle in order to benefit from the latest bug fixes and performance improvements.

Upgrade path

Downgrade is not supported.

If upgrading to the same "major.minor" upgrade bundle version, you can pick any higher patch version.

9.3.patch → 9.3.higher-patch

9.4.patch → 9.4.higher-patch

9.6.patch → 9.6.higher-patch

9.7.patch → 9.7.higher-patch

10.0.patch → 10.0.higher-patch

If upgrading to a another "major.minor" upgrade bundle version, you must pick the latest patch version.

9.3.patch → 9.4.latest-patch

9.3.patch → 9.5.latest-patch

9.6.patch → 9.7.latest-patch

9.7.patch → 10.0.latest-patch

BTPT bundle and OVA compatibility

Migration from V9.7.x to V10.0.x

1. Upgrade 9.7. patch → 9.7. latest-patch

2. Download the DB backup from the TradeSense dashboard and store it locally

3. Redeploy the node with latest OVA 2.1

4. Perform the upgrade process from v10.0.1 to v10.0.6.

5. Restore the DB on the upgraded v10.0.6 node from SSH and upgrade the node to the latest v10.0.x.

Note: The above process should be followed if the new OVA is redeployed for 9.7.x as well. The DB backup option is available from 9.7.11

Upgrade process

1. Pre-upgrade snapshot

2. Delete old cdrs

3. Deploy an upgrade bundle on the TSS

4. Trigger the automatic upgrade process

5. Wait for upgrade completion

6. Point TradeSense to the right TSS version

7. Updating missing severity details for alerts and incidents(Optional)

8. Archiving all active incidents(Optional)

Pre-upgrade snapshot

Upgrades are thoroughly tested and should happen smoothly. Yet, as a best practice, it as highly advised to take a snapshot of the TradeSense VA before proceeding any further in order to be able to rollback if need be.

However the snapshot needs to be deleted right after the upgrade is confirmed successful to avoid impacting the performance of the VM.

Refer to your hypervisor manual on how to do so.

      Deleting old CDRS

Below is the procedure to delete old CDRs when you are upgrading from <= 9.5.12.5 or <=9.4.17.13 or <=9.7.1.5 to latest version.

1. Connect to TradeSense system with WinSCP.

2. Copy delete_old_cdrs.py script file to /var/lib/docker_volumes/assure_log/_data in TradeSense system through WinSCP

3. SSH/VM console to TradeSense system

4. Run “stack exec assure_assure bash”command to go inside assure container

5. Execute "/opt/ipt/assure/venv/bin/python /opt/ipt/var/log/delete_old_cdrs.py -r 10" command to delete CDRs which are older than 10 days.

​

Deploy an upgrade bundle on the TSS

Prerequisites

The upgrade bundle must be available on a FTP server in order to be deployed on the TSS.

Deployment

To list the currently deployed upgrade bundles or to deploy new ones, go to System > Firmware Management, click on the BT Productivity Tools tab.

To deploy a new firmware, click "Add package".

Provide the FTP information and the absolute path to the folder containing the upgrade bundle.

Click "Ok".

Select the upgrade bundle file.

Click "Ok".

The TSS will then download the bundle from the configured FTP server, uncompress and deploy it in the appropriate folders.

When the deployment is complete, the bundle will be listed in System > Firmware Management, under the BT Productivity Tools tab.

Trigger the automatic upgrade process

Now that an upgrade bundle has been deployed on the TSS, it can be associated to a TradeSense node.

Go to Device Management > Productivity Tools Clusters, click on the desired cluster name.

In the "BTPT version" dropdown list, select the desired target version (please refer to the Upgrade path section to determine a safe upgrade path).

Click "Update".

Wait for upgrade completion.

Go to Devices Management > Productivity Tools Clusters, click on the desired cluster name, click on the Nodes tab.

Once the upgrade process has completed, the "Current Firmware" will match the target one.

Point TradeSense to the right TSS version

If TradeSense doesn't point to the right TSS version, repeat the TSS configuration on the TradeSense VM.

      Updating missing severity details for alerts and incidents

Below is the procedure to update severity details when you are upgrading from <= 9.5.12.5 or <=9.4.17.13 or <=9.7.1.5 to latest version.

1. Enable Maintenance mode in Assure

2. SSH/VM console to TradeSense  system

3. Run “stack exec assure_assure bash” command to go inside assure container

4. Execute "/opt/ipt/assure/venv/bin/flask update-alerts-incidents-current-severity" command

5. Disable Maintenance mode in Assure

    Archiving all active incidents

Below is the procedure to archive all active incidents when you are upgrading from <= 9.5.12.5 or <=9.4.17.13 or <=9.7.1.5 to latest version.

1. Enable Maintenance mode in Assure

2. SSH/VM console to TradeSense system​

3. Run “stack exec assure_assure bash” command to go inside assure container

4. Execute "/opt/ipt/assure/venv/bin/flask archive-active-incidents" command

5. Disable Maintenance mode in Assure​