1. Upgrade storage nodes

If your storage node runs in the same Virtual Machine or Operating System as your cluster node, skip this step. Otherwise upgrade all storage nodes one at a time by running:

[squirro@storagenode01 ~] sudo yum update -y

2. Upgrade all squirro cluster nodes

[squirro@clusternode01 ~] sudo yum update -y

3. Multi-node clusters only: Resolve /etc/squirro/topic.ini configuration

The Squirro packages attempt to upgrade *.ini and *.conf configuration files automatically. However if you have made local modifications such as those necessary to run multi-node Squirro Clusters, the upgrade results in *.rpmnew files that you would need to merge manually. We recommend

1. backing up the previous *.ini and *.conf files to *.ini.orig and *.conf.orig,
2. renaming the *.ini.rpmnew and *.conf.rpmnew files to *.ini and *.conf respectively
3. inspecting all the *.orig files individually and porting any settings manually

Use the following scripts to look for and resolve unresolved configuration files on each cluster node:

# 1. First remember all *.rpmnew because we are about to rename them, but we want to remember the list for step 3 below
sudo su
FILES_TO_RESOLVE=`ls /etc/squirro/*.ini.rpmnew /etc/nginx/conf.d/*.conf.rpmnew /etc/monit.d/*.rpmnew 2> /dev/null | sed -e "s/\.rpmnew//"`
  
# 2. Back up original config files and make the *.rpmnew files the real configuration files
# (\cp and \rm are used to avoid interactive alias of the commands and to ensure that the config file retains the ownership of the original config file)
for CONFIG_FILE in ${FILES_TO_RESOLVE}; do \cp ${CONFIG_FILE} ${CONFIG_FILE}.orig; \cp ${CONFIG_FILE}.rpmnew ${CONFIG_FILE}; \rm ${CONFIG_FILE}.rpmnew; done
  
# 3. Finally merge the commands. Exit vim via :q<enter>:q<enter> to accept a new config files verbatim
for CONFIG_FILE in ${FILES_TO_RESOLVE}; do vim -O ${CONFIG_FILE}.orig ${CONFIG_FILE}; done