ILP Update to version 2.8.0

1. Prerequisites

Before starting the upgrade, verify that the system is correctly generating SCORE (CONTEXT and MOTION) data.
To confirm this, perform several SSP login operations and ensure that the corresponding SCORE entries are recorded. If SCORE data is not being generated, investigate and resolve the issue before proceeding with the upgrade.
Please be advised that for the Webapp servers, you will need approximately 20GB of free disk space to perform the upgrade.
On all UBA Webapp Servers / VeridiumID Persistence Servers you need to have an username with “sudo” privileges in order to be able to run the scrips.

2. Create and Prepare the Temporary Update Directory (on each node - UBA WebApp)

CODE

TMP_DEST="/vid-app/update280"
sudo mkdir -p $TMP_DEST && sudo chown $(whoami):$(whoami) $TMP_DEST && sudo chmod 755 $TMP_DEST

3. Download the UBA archive (on each node - only on UBA WebApp)

Name	URL	SHA256	MD5
uba-onprem-installer-2.8.0.zip	https://veridium-repo.veridium-dev.com/repository/UBAInstallerOnPrem/2.8.0/uba-onprem-installer-2.8.0.zip	a34c926a3241b8c8d4c92fae12b0f4fecee285ea	c77c32ef97b80e9643977adb913c3cf8

CODE

# Please replace <nexusUser> / <nexusPassword> with your nexus credentials
TMP_DEST="/vid-app/update280"
sudo wget -P $TMP_DEST --user <nexusUser> --password <nexusPassword> https://veridium-repo.veridium-dev.com/repository/UBAInstallerOnPrem/2.8.0/uba-onprem-installer-2.8.0.zip 
sudo unzip ${TMP_DEST}/uba-onprem-installer-2.8.0.zip -d ${TMP_DEST}

4. Start the update process

Run the following command on one server at a time, only on the UBA Webapp nodes:

CODE

TMP_DEST="/vid-app/update280"
sudo bash ${TMP_DEST}/uba-onprem-installer/update-procedure/update.sh 2.8.0

If the UBA services are not running, and you have manually remediated the issue, run the following command to switch to version 2.8.0:

CODE

sudo sed -i "s/UBA_VERSION.*/UBA_VERSION=2.8.0/g" /etc/default/veridiumid/uba_variables

5. Update Persistence nodes

Run the following commands with root:

CODE

systemctl stop uba-kafka
if [ ! -L "/opt/veridiumid/uba" ] && [ -d "/opt/veridiumid/uba" ]; then mv /opt/veridiumid/uba /vid-app/1.0.0/ 2>/dev/null ; rm -rf /opt/veridiumid/uba ; ln -s "/vid-app/1.0.0/uba" "/opt/veridiumid/uba" ; fi
if [ ! -L "/var/log/veridiumid/uba" ] && [ -d "/var/log/veridiumid/uba" ]; then mv /var/log/veridiumid/uba /vid-app/dyn/logs/ 2>/dev/null; rm -rf /var/log/veridiumid/uba ; ln -s "/vid-app/dyn/logs/uba" "/var/log/veridiumid/uba"; fi
systemctl start uba-kafka
sed -i "s/UBA_VERSION.*/UBA_VERSION=2.8.0/g" /etc/default/veridiumid/uba_variables

⚠️ Important – Zookeeper Authentication Setup (Version 2.7.8+)

Starting with version 2.7.8, you can configure authentication on Zookeeper nodes.

1. Set Zookeeper properties on ILP WebApp nodes

You must set the correct values for username, password, and encrypt.salt in /etc/default/veridiumid/zookeeper.properties on all ILP WebApp nodes, copying them from a persistence node.

Retrieve existing credentials from a persistence node:

CODE

sudo cat /etc/veridiumid/zookeeper.properties

Copy the following values to /etc/default/veridiumid/zookeeper.properties on all WebApp nodes:

username
password
encrypt.salt

2. Set the script path and setup the Zookeeper authentication

Run the following commands on a single ILP webapp node in each datacenter:

CODE

##to setup authentication
sudo -u veridiumid bash -c "/vid-app/ubavenv/bin/python /opt/veridiumid/uba/scripts/setupZookeeperAcl.py setup"

Restart uba services on all ILP webapp nodes:

CODE

uba_stop
uba_start

If there are issues, runt this command to revert zookeeper authentication.

CODE

##to remove authentication
sudo -u veridiumid bash -c "/vid-app/ubavenv/bin/python /opt/veridiumid/uba/scripts/setupZookeeperAcl.py remove"

⚠️ Important – Filebeat Setup (Version 2.8.0+)

Starting with version 2.8.0, you can configure filebeat service.

1. Copy tenant-infra.yaml on ILP WebApp nodes from Websecadmin

Path: /opt/veridiumid/filebeat/config/tenant-infra.yaml

CODE

sudo mkdir -p /opt/veridiumid/filebeat/config
sudo vi /opt/veridiumid/filebeat/config/tenant-infra.yaml

Run script to setup filebeat

CODE

TMP_DEST="/vid-app/update280"
sudo /bin/bash ${TMP_DEST}/uba-onprem-installer/update-procedure/resources/scripts/all/setupFilebeat.sh

For MyVid - run manually on a persistence node:

CODE

cqlsh
use uba;
ALTER TABLE uba.v2_context_data_indexed_by_id_and_tenant WITH default_time_to_live = 2592000;  
ALTER TABLE uba.v2_context_data_indexed_by_stage_id_and_tenant WITH default_time_to_live = 2592000;