Upgrade VeridiumID from 3.5.x to v3.6.0 (without OS Upgrade)

## download the package on each server; the below command can be used. Please fill in the proxy IP and username and password provided by Veridium.
## it is recommanded to execute these commands with the user that is going to do the installation.
## based on OS version, you have download the necessary package:
## RHEL7, Centos7
wget --user NEXUS_USER --password NEXUS_PASSWORD -e use_proxy=yes -e http_proxy=PROXY_IP:PROXY_PORT https://veridium-repo.veridium-dev.com/repository/VeridiumUtils/Veridium-3.6.0-update/veridiumid-update-packages-10.0.55.zip
## RHEL8, Rocky8
wget --user NEXUS_USER --password NEXUS_PASSWORD -e use_proxy=yes -e http_proxy=PROXY_IP:PROXY_PORT https://veridium-repo.veridium-dev.com/repository/VeridiumUtils/Veridium-3.6.0-update/veridiumid-update-packages-rhel8-10.0.55.zip
## RHEL9, Rocky9
wget --user NEXUS_USER --password NEXUS_PASSWORD -e use_proxy=yes -e http_proxy=PROXY_IP:PROXY_PORT https://veridium-repo.veridium-dev.com/repository/VeridiumUtils/Veridium-3.6.0-update/veridiumid-update-packages-rhel9-10.0.55.zip

python3 --version

TMP_DEST="/home/veridiumid/update360"
#### please choose the one that apply, based on your OS:
##RHEL7
unzip veridiumid-update-packages-10.0.55.zip -d ${TMP_DEST}
##RHEL8
unzip veridiumid-update-packages-rhel8-10.0.55.zip -d ${TMP_DEST}
##RHEL9
unzip veridiumid-update-packages-rhel9-10.0.55.zip -d ${TMP_DEST}

## PLEASE INSTALL JAVA 11 from local repositories; it should be OPENJDK distribution. Without this step the update will not be possible
sudo yum install java-11-openjdk -y
## before the update, java 8 still should be the default one; check by running:
java -version
## if JAVA 8 is not the current java, please change it using below command, and select option for JAVA8
sudo update-alternatives --config java

TMP_DEST="/home/veridiumid/update360"
sudo yum localinstall -y ${TMP_DEST}/packages/veridiumid_update_procedure-10.0.55-20240425.x86_64.rpm
sudo python3 /etc/veridiumid/update-procedure/current/preUpdateSteps.py --version 10.0.55 --rpm-path ${TMP_DEST}/packages/
sudo python3 /etc/veridiumid/update-procedure/current/startUpdate.py --version 10.0.55 --rpm-path ${TMP_DEST}/packages/
sudo bash /etc/veridiumid/scripts/check_services.sh

KIBANA_LOG=$(dirname $(readlink /var/log/veridiumid/kibana))
KIBANA_DIR=$(dirname $(readlink /opt/veridiumid/kibana))
sudo rm -rf ${KIBANA_LOG}/kibana
sudo rm -rf ${KIBANA_DIR}/kibana
sudo rm -rf /opt/veridiumid/kibana
sudo rm -rf /etc/veridiumid/kibana
sudo rm -rf /var/log/veridiumid/kibana
sudo python3 /etc/veridiumid/update-procedure/current/startUpdate.py --version 10.0.55 --rpm-path ${TMP_DEST}/packages/

TMP_DEST="/home/veridiumid/update360"
sudo bash /etc/veridiumid/update-procedure/current/resources/scripts/360/update_cassandra.sh ${TMP_DEST}/packages/
##check status
sudo /opt/veridiumid/cassandra/bin/nodetool status
sudo /opt/veridiumid/cassandra/bin/nodetool describecluster
## to edit crontab run:
##   sudo crontab -e
## to list crontab run:
##   sudo crontab -l
## also please comment this line on 2 out of 3 servers:
#0 1 * * 5 bash /opt/veridiumid/cassandra/conf/cassandra_maintenance.sh -c /opt/veridiumid/cassandra/conf/maintenance.conf
## this is running repair, but it should not run in parallel on all 3 nodes in the same datacenter.
## also there should be at least 3 hours difference between the repair operation and the other maintainence task, the one that ends with -k
## The line with -k should be in crontab on all 3 nodes, uncommented.
## if number of devices are not seen in websecadmin, please recreate lucene indices
bash /opt/veridiumid/cassandra/conf/recreateCassandraLuceneIndexes.sh -c /opt/veridiumid/cassandra/conf/maintenance.conf

sudo yum install java-11-openjdk -y
## before the update, java 8 still should be the default one; check by running:
java --version
## if JAVA 8 is not the current java, please change it using below command, and select option for JAVA8
sudo update-alternatives --config java

## check installed package
sudo yum list installed veridiumid_update_procedure
## check availability of the new package; if this package is not available, please fix the issue with the repository
sudo yum list available veridiumid_update_procedure-10.0.55-20240425

sudo yum clean metadata
sudo yum install -y veridiumid_update_procedure-10.0.55
sudo python3 /etc/veridiumid/update-procedure/current/preUpdateSteps.py --version 10.0.55 --use-repo
sudo python3 /etc/veridiumid/update-procedure/current/startUpdate.py --version 10.0.55 --use-repo
sudo bash /etc/veridiumid/scripts/check_services.sh

KIBANA_LOG=$(dirname $(readlink /var/log/veridiumid/kibana))
KIBANA_DIR=$(dirname $(readlink /opt/veridiumid/kibana))
sudo rm -rf ${KIBANA_LOG}/kibana
sudo rm -rf ${KIBANA_DIR}/kibana
sudo rm -rf /opt/veridiumid/kibana
sudo rm -rf /etc/veridiumid/kibana
sudo rm -rf /var/log/veridiumid/kibana
sudo python3 /etc/veridiumid/update-procedure/current/startUpdate.py --version 10.0.55 --use-repo

sudo sed -i 's|\${build_date}\ |\${build_date}\*\ |g' /etc/veridiumid/update-procedure/current/resources/scripts/360/update_cassandra.sh
sudo bash /etc/veridiumid/update-procedure/current/resources/scripts/360/update_cassandra.sh
##check status and wait till it starts before going to next node
sudo /opt/veridiumid/cassandra/bin/nodetool status
sudo /opt/veridiumid/cassandra/bin/nodetool describecluster
## to edit crontab run:
##   sudo crontab -e
## to list crontab run:
##   sudo crontab -l
## also please comment this line on 2 out of 3 servers:
#0 1 * * 5 bash /opt/veridiumid/cassandra/conf/cassandra_maintenance.sh -c /opt/veridiumid/cassandra/conf/maintenance.conf
## this is running repair, but it should not run in parallel on all 3 nodes in the same datacenter.
## also there should be at least 3 hours difference between the repair operation and the other maintainence task, the one that ends with -k
## The line with -k should be in crontab on all 3 nodes, uncommented. 
## if number of devices are not seen in websecadmin, please recreate lucene indices
sudo bash /opt/veridiumid/cassandra/conf/recreateCassandraLuceneIndexes.sh -c /opt/veridiumid/cassandra/conf/maintenance.conf

bash /etc/veridiumid/update-procedure/current/resources/scripts/360/reinitApp.sh

sudo grep -q "max-old-space-size" /opt/veridiumid/kibana/config/node.options || sudo echo -ne "\n--max-old-space-size=512\n" >> /opt/veridiumid/kibana/config/node.options
systemctl restart ver_kibana

sudo /opt/veridiumid/cassandra/bin/cqlsh --cqlshrc=/opt/veridiumid/cassandra/conf/veridiumid_cqlshrc --ssl -e "UPDATE veridium.wizard SET steps_statuses = {'/setup/setupPermissions' :false,'/setup/setupMessages': false,'/setup/setupSmsTemplates' : false,'/setup/migrateMobileVersions' : false,'/integrations/updateEnrollmentStep' : false,'/setup/orchestrator/rules/cmd_otp_only/update' : false,'/setup/customApplication' : false},ended = false,started = false,muted = false WHERE id = 'bf0ed51e-337f-4b97-b4f5-d2b0caa74000';"

## on RHEL7/Centos7 it should be used python 3.6
python3 --version
##Python 3.6.8
yum -y install python3.6
## on RHEL8/RHEL9 it should be used python3.9
sudo yum -y install python39 python39-pip
##Python 3.9.18