Update from version 2.7.0 -> 2.7.2

Before you START THE UPGRADE please check if you get SCORE (CONTEXT and MOTION). In order to do this please do a few SSP LOGIN.

Please be advised that for the Webapp servers, you will need approximately 50GB of free disk space to perform the upgrade.

You need to have ssh access on all ILP Webapp Servers / VeridiumID Persistence Servers from the server where “variables.yaml“ is located (check Step 3)

On all ILP Webapp Servers / VeridiumID Persistence Servers you need to have an username with “sudo” privileges.

The update is required to be run on one of the persistence machines and on each webapps machines.

Open a terminal for one of the persistence Persistence Servers and connect via SSH to the Persistence Servers.

CODE

# Please replace <nexusUser> / <nexusPassword> with your nexus credentials
# Download "update-persistence-272.zip" on one persistence server
wget --user <nexusUser> --password <nexusPassword> https://veridium-repo.veridium-dev.com/repository/UBAInstallerOnPrem/2.7.2/update-persistence-272.zip
unzip update-persistence-272.zip

Open a terminat for each ILP Webapp Servers and connect via SSH to the ILP Webapp Servers.

CODE

# Please replace <nexusUser> / <nexusPassword> with your nexus credentials
# Download "uba-webapp-update-272.zip" on each ILP Webapp server
wget --user <nexusUser> --password <nexusPassword> https://veridium-repo.veridium-dev.com/repository/UBAInstallerOnPrem/2.7.2/uba-webapp-update-272.zip
unzip uba-webapp-update-272.zip

In order to start the upgrade we need “variables.yaml” file, file was used when ILP has been installed (old path: uba-onprem-installer/variables.yaml).

CODE

# If you don't know where the file is please use the below command on the server where UBA was installed (if you don't remember which server, run the command to all UBA servers):
sudo find / -type f -name "variables.yaml"

The output will be something like: /home/<username>/uba-onprem-installer/variables.yaml

Below you will find “/home/<username>/uba-onprem-installer/variables.yaml“ please replace it with your file path.

Copy the file “/home/<username>/uba-onprem-installer/variables.yaml” to ILP folder:

CODE

# Please replace "/home/<username>/uba-onprem-installer/variables.yaml" with your variables.yaml file path
sudo cp /home/<username>/uba-onprem-installer/variables.yaml /opt/veridiumid/uba/variables.yaml
sudo chown veridiumid:veridiumid /opt/veridiumid/uba/variables.yaml

After you complete STEP 3, please copy /opt/veridiumid/uba/variables.yaml file on each ILP Webapp Server / Veridium Persistence

CODE

Please replace <USERNAME> and <SERVER_IP> with your username/server ip.
scp /opt/veridiumid/uba/variables.yaml <USERNAME>@<SERVER_IP>:.
ssh <USERNAME>@<SERVER_IP>
sudo cp variables.yaml /opt/veridiumid/uba/variables.yaml
sudo chown veridiumid:veridiumid /opt/veridiumid/uba/variables.yaml

From a ILP Webapp Server we need to copy “/etc/default/veridiumid/uba_variables" on one Veridium Persistence, where we are gonna do the install.

CODE

scp /etc/default/veridiumid/uba_variables <USERNAME>@<SERVER_VERIDIUM_PERSISTENCE_IP>:.
ssh <USERNAME>@<SERVER_VERIDIUM_PERSISTENCE_IP>
sudo cp uba_variables /etc/default/veridiumid/uba_variables
sudo chown root:root /etc/default/veridiumid/uba_variables

From a ILP Persistence Server we need to two files “/opt/veridiumid/cassandra/conf/cqlsh_cassandra_cert.pem" and “/opt/veridiumid/cassandra/conf/cqlsh_cassandra_key.pem“ to each ILP Webapp Server.

CODE

# Go to the persistence machine with ssh
ssh <USERNAME>@<SERVER_VERIDIUM_PERSISTENCE_IP>
scp /opt/veridiumid/cassandra/conf/cqlsh_cassandra_cert.pem <USERNAME>@<SERVER_IP1>:.
scp /opt/veridiumid/cassandra/conf/cqlsh_cassandra_cert.pem <USERNAME>@<SERVER_IP2>:.
scp /opt/veridiumid/cassandra/conf/cqlsh_cassandra_key.pem <USERNAME>@<SERVER_IP1>:.
scp /opt/veridiumid/cassandra/conf/cqlsh_cassandra_key.pem <USERNAME>@<SERVER_IP2>:.

Start the UPDATE on one of the Veridium Persistence Servers

Copy “update-persistence-272.zip“ on one Veridium Persistence Servers

CODE

# Go where you have the archive update-persistence-272.zip and folder update-persistence. Let's presume your archive and extracted files/folder are in ~/
# !!!! Copy your variables.yaml modified file to update-persistence folder.
sudo cp /opt/veridiumid/uba/variables.yaml ~/update-persistence/variables.yaml
cd ~/update-persistence
# IF IS THE FIRST PERSISTENCE SERVER UPDATE YOU NEED TO RUN the following command to start the update:
/bin/bash update-persistence.sh DATACENTER_CASSANDRA
# Check the services:
sudo /bin/bash /opt/veridiumid/uba/scripts/uba_check_services.sh
sudo cp variables.yaml /opt/veridiumid/uba/variables.yaml
sudo chown veridiumid:veridiumid /opt/veridiumid/uba/variables.yaml
# This step must be ran only on one persistence server

Start the UPDATE on ILP WEBAPP Servers

Copy “uba-webapp-update-272.zip“ on each ILP WEBAPP Servers

CODE

# !!!! Copy your variables.yaml to update-uba-webapp folder and the two files we took from the persistence machines
sudo cp /opt/veridiumid/uba/variables.yaml ~/update-uba-webapp/variables.yaml
sudo cp ~/cqlsh_cassandra_cert.pem ~/update-uba-webapp/cqlsh_cassandra_cert.pem
sudo cp ~/cqlsh_cassandra_key.pem ~/update-uba-webapp/cqlsh_cassandra_key.pem
# Start the update
cd update-uba-webapp
/bin/bash uba-update.sh DATACENTER_CASSANDRA
# Check the services:
sudo /bin/bash /opt/veridiumid/uba/scripts/uba_check_services.sh
sudo cp variables.yaml /opt/veridiumid/uba/variables.yaml
sudo chown veridiumid:veridiumid /opt/veridiumid/uba/variables.yaml
# add opentelemetry-collector$DOMAIN_SEPARATOR$DOMAIN_NAME (like opentelemetry-collector.dev15.veridium-dev.com) in /etc/hosts 
# with the IP of the machine
WEBAPP_IP opentelemetry-collector$DOMAIN_SEPARATOR$DOMAIN_NAME
Do a SSP Login in your WebAPP

Go to the next ILP WEBAPP Server and do the same steps.

Start the ILP-CANNARY service (on one of the ILP-webapp-servers)-OPTIONAL

Choose one ILP WEBAPP SERVER and start manually the “uba-cannary” service:

CODE

sudo systemctl start uba-cannary

check the logs from:

/var/log/veridiumid/uba/uba-cannary.log

based on variable “CANARY_RUN_PERIOD“ set from “/etc/default/veridiumid/uba_variables”, if the value is 60 will be: 60 seconds x 11 authentication = 11 minutes.

and we will see SCORE:

CODE

...truncate...
INFO  com.veridiumid.uba.v2.cannary.MotionContextClientService:350 - Context result answer: ACCEPT confidence HIGH score 0.25694302675560166
...truncate...
INFO  com.veridiumid.uba.v2.cannary.MotionContextClientService:291 - UBA score: 0.7028731166294203 for stage ID 4f374442-9e8d-4687-94fb-c8918a24c2a5
...truncate...

Update the configuration on veridiumid-server WEBAPP servers:

On the webapp machines of veridiumid-server (on each machine), we need to add the following lines in /opt/veridiumid/tomcat/bin/setenv.sh file:

CODE

### go in setenv in tomcat and add the following
TRACING_AGGREGATE_SPAN="true"

After that, you need to restart tomcat on both machine:

CODE

sudo service ver_tomcat restart
# wait for the servers to restart succesfully