Upgrade Abiquo HA platform to v5.2.x

This section describes how to upgrade from Abiquo 4.7.0 or above to the current Abiquo version. Please contact Abiquo Support for further information.

Major upgrade

The upgrade to Abiquo 5.2.0 is a major upgrade with upgrades of third-party software packages that are critical platform dependencies

You must make snapshots of ALL servers before you start the upgrade

Abiquo YUM repositories are no longer open, please contact Abiquo Support to obtain your credentials
This upgrade process starts from Abiquo 4.7 or above. To upgrade from earlier versions, please contact Abiquo Support

1. Prepare branding

If you are upgrading from Abiquo 4.7.x, the new UI in Abiquo 5.0 requires new branding. See Abiquo branding guide

2. Prevent cloud users from performing VM operations

In the UI in the Infrastructure view, select each physical machine and click Disable
Using the API, set the state of each physical machine to DISABLED

3. Check for operations in progress on the platform

Before you shut down the platform servers you should check that no operations are in progress on the platform.

Check that the Abiquo RabbitMQ queues are empty on the Abiquo Monolithic Server, Abiquo Server or Datanode server

The number of messages in all queues must be 0.

# rabbitmqctl list_queues messages name

# rabbitmqctl list_queues messages name
Listing queues ...
0	abiquo.am.notifications
0	abiquo.bpm.notifications
0	abiquo.datacenter.requests.ADatacenter.bpm
0	abiquo.datacenter.requests.ADatacenter.virtualfactory
0	abiquo.ha.tasks
0	abiquo.nodecollector.notifications
0	abiquo.pcrsync.messages
0	abiquo.pcrsync.parking-expect-no-consumers
0	abiquo.scheduler.fast.requests
0	abiquo.scheduler.requests
0	abiquo.scheduler.slow.requests
0	abiquo.tracer.traces
0	abiquo.virtualfactory.notifications
0	abiquo.virtualmachines.definitionsyncs
0	abiquo.vsm.eventsynk
...done.

On the V2V Server, check for any active conversions by checking for the V2V or Mechadora processes
```
$ ps aux | grep v2v
$ ps aux | grep mechadora
```

When users' VM operations are blocked and all of the above checks show that no tasks are running, it is safe to halt the platform.

4. Back up the main platform elements

To perform a basic backup of the platform, run the following backups:

Before you begin, stop platform services, and check you have enough space on your destination systems.

# On DB server, back up the Abiquo MySQL DBs
mysqldump --routines --triggers kinton            > kinton.sql-$(date +%Y%m%d_%H%M%S)
mysqldump --routines --triggers kinton_accounting > kinton_accounting.sql-$(date +%Y%m%d_%H%M%S)

# On the Abiquo API Server or UI server, back up the UI
tar cvfz /var/www/html/ui.tgz-$(date +%Y%m%d_%H%M%S) /var/www/html/ui

# If you are using SAML authentication with multiple IdPs, on ALL Abiquo API Servers, back up this file
cp 
/opt/abiquo/tomcat/webapps/api/WEB-INF/classes/springresources/security/saml/security-saml-generated-beans.xml /opt/abiquo/tomcat/webapps/api/WEB-INF/classes/springresources/security/saml/security-saml-generated-beans.xml-$(date
 +%Y%m%d_%H%M%S)

# On ALL servers, back up the /opt/abiquo folder
tar cvfz /opt/abiquo.tgz-$(date +%Y%m%d_%H%M%S) /opt/abiquo

# On Abiquo Monolithic or API Server, Remote Services, or Datanode, back up Redis
redis-cli save
cp -a /var/lib/redis /var/lib/redis-$(date +%Y%m%d_%H%M%S)

If you are using HTTPS-SSL between your Tomcat servers, for each Tomcat server:

From the /opt/abiquo/tomcat/conf folder, back up the server.xml files. You will need to restore and modify them after the yum upgrade.

See Upgrade Tomcat 8 to Tomcat 9 with HTTPS TLS.

5. Disable old billing dashboards and delete last bills

In Abiquo 5.2, the billing dashboard feature is now in the core Abiquo platform.

If you are using the billing dashboard scripts from previous versions, disable them and delete last bills before you continue with the upgrade.

On the server where you were running the billing packages, remove the Cron jobs to run the billing scripts.
```
# rm /etc/cron.d/abiquo-billing-ec2
# rm /etc/cron.d/abiquo-billing-arm
```
Delete the last bills from the previous version of the billing dashboards (from the kinton.billing_consolidation and kinton.billing_register tables). Remove the bills for Azure and Amazon providers, for the number of months covered by the abiquo.enterprise.property.billing.monthoffset property, which has a default value of 2 months. Later the new billing dashboards feature will regenerate these bills.

6. Stop platform services

This section describes how to stop platform services on all servers.

if there are operations in progress, DO NOT STOP the platform services because this can cause serious issues with your platform. See Check for operations in progress on the platform and wait for all operations to complete

To stop platform services:

Stop the API on the API server or monolithic server
```
systemctl stop abiquo-tomcat
```
Stop the UI on the API server or monolithic server or dedicated UI server
```
systemctl stop httpd
```
Stop remote services server
```
systemctl stop abiquo-tomcat
```
Stop the database on the monolithic server or database server.
```
systemctl stop mariadb
```
For a datanode configuration, you will also need to stop the Galera cluster. For more details, see Stop and start HA configuration
Stop RabbitMQ (on the monolithic server or API Server or Datanode)
```
systemctl stop rabbitmq-server
```
V2V server -
You do not need to stop anything because the BPM remote service is run on-demand only

Stop monitoring server

systemctl stop abiquo-delorean
systemctl stop abiquo-emmett
systemctl stop kairosdb
systemctl stop cassandra

On the monitoring server, check if Cassandra is really dead
```
ps auwx | grep cassandra
```
Get the process number for Cassandra (the first number in the output of the previous command), and kill it. In this example, Cassandra is process 12345.
```
kill -9 12345
```

All processes on platform servers should now be halted.

7. Make snapshots and backups of all platform servers

The upgrade to Abiquo 5.2.x is a major upgrade with upgrades of third-party software packages that are critical platform dependencies

You MUST make snapshots of all servers in your platform before you upgrade to Abiquo 5.2.x.

8. Prepare yum repositories on all servers

Check that you have the repository URL and credentials
To upgrade to a version with a patch number of zero, for example, version 5.2.0

Click here to show/hide steps to upgrade to a 0 version

Remove the previous version Abiquo release packages.
```
yum remove 'abiquo-release-*'
```
Locate the corresponding abiquo-release-ee package in the list of available versions

Install the release package. For Abiquo 5.2.0, the command would be similar to the following

yum localinstall http://user:passwd@mirror.abiquo.com/el7/5.2/os/x86_64/abiquo-release-ee-5.2.0-XXXX.el7.noarch.rpm

Disable the updates repo. See https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/deployment_guide/sec-managing_yum_repositories

OR To upgrade to a version with patch number that is not zero, for example, version 5.2.1, enable both repositories:
```
yum-config-manager --enable abiquo-base
yum-config-manager --enable abiquo-updates
```

Optionally add your username and password to the Abiquo repos

yum-config-manager --save --setopt=abiquo-*.username=MYUSERNAME
yum-config-manager --save --setopt=abiquo-*.password=MYPASSWORD

Don't forget to use a backslash to escape any shell special characters. For more details, see https://www.oreilly.com/library/view/learning-the-bash/1565923472/ch01s09.html

Clean yum and make cache

yum clean all && yum makecache

If you did not make snapshots of all servers already, then do this now

Major upgrade

The upgrade to Abiquo 5.2.x is a major upgrade with upgrades of third-party software packages that are critical platform dependencies

You must make snapshots of ALL servers before you start the upgrade

9. Upgrade Datanode servers in HA

In a HA environment, RabbitMQ and MySQL may be together on a Datanode server.

Abiquo will upgrade to new versions of RabbitMQ and MySQL that require a manual upgrade path of dependencies.

These steps are for a server that contains RabbitMQ AND MySQL

Shut down the Galera cluster. See Stop and start HA configuration.

Remove the Erlang and Galera packages.

yum remove erlang* galera
yum clean all && yum makecache

Install new RabbitMQ and MariaDB server
```
yum install rabbitmq-server MariaDB-server
```
Before you confirm, check that the packages will be installed from the abiquo-base repository
1. rabbitmq-server: 3.8.2.1
2. MariaDB-server: 10.4.10.1
Upgrade Abiquo to 5.2.x
```
yum update
```
Before you confirm, check the following packages will be installed from the abiquo-base repository:
1. jdk: 11.0.6u10
2. redis: 5.0.7.1

Enable the new services

systemctl enable mariadb
systemctl enable rabbitmq-server

Edit the MySQL configuration to use the new version of Galera.
The configuration file can be found at
```
/etc/my.cnf.d/galera.cnf
```
Change the wsrep_provider line to use the new version of Galera (in the galera-4 folder)
```
wsrep_provider=/usr/lib64/galera-4/libgalera_smm.so
```
Start Galera, which will also start MySQL.
Check the Galera state data.
```
cat /var/lib/mysql/grastate.dat
```
Find the server which is safe to bootstrap
```
safte_to_bootstrap: 1
```
Start Galera
```
galera_new_cluster
```
On the other servers in the cluster, start MariaDB
```
systemctl start mariadb
```
For more details see Stop and start HA configuration
Start RabbitMQ on all datanode servers
```
systemctl start rabbitmq-server
```
Upgrade MySQL on all datanode servers
```
mysql_upgrade
```
The mysql_upgrade step may detect errors that trigger messages such as the following:
kinton_accounting.ACCOUNT_PERIOD_USAGE_VW Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 100129, now running 100410. Please use mysql_upgrade to fix this error
These messages are expected and this same mysql_upgrade process will automatically fix these errors in its next stages.
Check that the mysql_upgrade process completes correctly.
Check that your hostname is in your DNS or in your /etc/hosts file
Upgrade the Abiquo API databases. This script is available on the API Server.
```
abiquo-db [-h DB hostname] [-P DB port] [-u user] [-p password] update
```
If the liquibase update fails with a message similar to the following:
Liquibase update Failed: Validation Failed:
1 change sets check sum
src/X.X.X-XX/kinton-X.X.X.xml::ABICLOUDPREMIUM-XXXX-XxxxxxxxXXxXxxxxxxXxxxxx::XXXXXXXXX is now: 7:ee2fa6e058ec76c7abf801567898917d
For more information, use the --logLevel flag
Do the following steps
1. Clear the database checksums
  abiquo-db clearCheckSums
2. Retry the above abiquo-db update command.

10. Upgrade UI servers in HA

This step is for standalone UI servers only.

On each separate UI Server, upgrade Abiquo.
```
yum clean all && yum makecache
yum update
```
This will update Abiquo to version 5.2.x.
Remember to perform the UI configuration steps later in the upgrade before restarting the HTTP service.

11. Upgrade load balanced API servers in HA

This step is for API servers in an HA environment, where there is a separate datanode that contains the database and RabbitMQ.

On the API servers, upgrade Abiquo to 5.2.x
```
yum update
```
Before you confirm, check the following packages will be installed from the abiquo-base repository:
1. jdk: 11.0.6u10
2. redis: 5.0.7.1

Check versions of Java and Tomcat

Click here to show/hide steps to check versions

Check that the symbolic link to the latest version of Java points to Java 11

# cd /usr/java
# ll
latest -> /usr/java/jdk-11.0.6+10

Check that the correct Tomcat version will be used

# cd /opt/abiquo/tomcat/bin
# sh version.sh
Using CATALINA_BASE:   /opt/abiquo/tomcat
Using CATALINA_HOME:   /opt/abiquo/tomcat
Using CATALINA_TMPDIR: /opt/abiquo/tomcat/temp
Using JRE_HOME:        /usr
Using CLASSPATH:       /opt/abiquo/tomcat/bin/bootstrap.jar:/opt/abiquo/tomcat/bin/tomcat-juli.jar
NOTE: Picked up JDK_JAVA_OPTIONS:  --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED
Server version: Apache Tomcat/9.0.33
Server built:   Mar 11 2020 09:31:38 UTC
Server number:  9.0.33.0
OS Name:        Linux
OS Version:     3.10.0-1160.15.2.el7.x86_64
Architecture:   amd64
JVM Version:    11.0.6+10
JVM Vendor:     AdoptOpenJDK

On the API Server in the JDK folder, check certificate migration for AM download. The API Server certificate should be listed for Java 11 with its FQDN. You may need to enter the storepass option to supply the password and you can use the alias option to search for the hostname or FQDN of your server

# cd /usr/java/jdk-11.0.6+10/lib/security
# keytool -list -keystore cacerts -alias (hostname or fqdn)

For example

sudo keytool -list -keystore cacerts -alias abiquo.example.com

On the API Servers, change file permissions so the Abiquo services can run as the tomcat user (not root) and allow access to the configuration files
```
chown -R tomcat /opt/abiquo
```

12. Upgrade remote services servers

These steps are for remote services servers in a distributed or HA environment.

Upgrade EVERY remote services server with these steps.

On the remote services servers, upgrade Abiquo to 5.2.x
```
yum update
```
Before you confirm, check the following packages will be installed from the abiquo-base repository:
1. jdk: 11.0.6u10
2. redis: 5.0.7.1

After the update, check versions of Java and Tomcat

Click here to show/hide steps to check versions

Check that the symbolic link to the latest version of Java points to Java 11

# cd /usr/java
# ll
latest -> /usr/java/jdk-11.0.6+10

Check that the correct Tomcat version will be used

# cd /opt/abiquo/tomcat/bin
# sh version.sh
Using CATALINA_BASE:   /opt/abiquo/tomcat
Using CATALINA_HOME:   /opt/abiquo/tomcat
Using CATALINA_TMPDIR: /opt/abiquo/tomcat/temp
Using JRE_HOME:        /usr
Using CLASSPATH:       /opt/abiquo/tomcat/bin/bootstrap.jar:/opt/abiquo/tomcat/bin/tomcat-juli.jar
NOTE: Picked up JDK_JAVA_OPTIONS:  --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED
Server version: Apache Tomcat/9.0.33
Server built:   Mar 11 2020 09:31:38 UTC
Server number:  9.0.33.0
OS Name:        Linux
OS Version:     3.10.0-1160.15.2.el7.x86_64
Architecture:   amd64
JVM Version:    11.0.6+10
JVM Vendor:     AdoptOpenJDK

On the remote services server in the JDK folder, check certificate migration to allow AM download

The API server certificate should be listed for Java 11 with its FQDN. You may need to enter the storepass option to supply the password and you can use the alias option to search for the hostname or FQDN of your server

# cd /usr/java/jdk-11.0.6+10/lib/security
# keytool -list -keystore cacerts -alias (hostname or fqdn)

For example

sudo keytool -list -keystore cacerts -alias abiquo.example.com

On all remote services servers using SSL
Edit the Tomcat server configuration file:
```
/opt/abiquo/tomcat/conf/server.xml
```
Find the location of the certificate files for Java 8
```
keystoreFile="/usr/java/default/jre/lib/security/cacerts"
```
Change it to the location for Java 11 (e.g. remove "/jre")
```
keystoreFile="/usr/java/default/lib/security/cacerts" 
```
On all remote services servers, change file owners to tomcat user
```
chown -R tomcat /opt/abiquo
```
On the remote services with appliance manager and the V2V server (i.e. servers that mount the NFS repository), change file owners to Tomcat user
```
chown -R tomcat /opt/vm_repository
chmod -R a+r /opt/vm_repository
```

13. Upgrade monitoring server

This step is for Watchtower monitoring servers in all installations.

To continue using Java 8 (for Cassandra), remove the JDK through the package manager. If you use yum, it will be delete all the dependencies and you will have to reinstall them
```
rpm -e --nodeps jdk
```
Check the jdk to install is version 8
```
rpm -qa | grep jdk
```

Check that Java is correctly installed:

If you execute this command and get that error, please execute the command from the next bullet:
```
$ java
-bash: java: command not found
```

Fix it by executing this command, then selecting the option "java-1.8.0-openjdk.x86_64 (/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.292.b10-1.el7_9.x86_64/jre/bin/java)":

$ sudo alternatives --config java

There are 3 programs which provide 'java'.

  Selection    Command
-----------------------------------------------
   1           /usr/java/jdk1.8.0_144/bin/java
 + 2           /usr/java/jdk-11.0.6+10/bin/java
*  3           java-1.8.0-openjdk.x86_64 (/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.292.b10-1.el7_9.x86_64/jre/bin/java)

Enter to keep the current selection[+], or type selection number: 3

As for the Abiquo DB steps, remove Galera, which will also remove MariaDB
```
yum remove galera
```
Clean yum and make cache
```
yum clean all && yum makecache
```
Install MariaDB
```
yum install MariaDB-server
```
Update Abiquo
```
yum update
```
Check that the Java package is now "javajdk" to use Java 1.8.0u144 with Cassandra:
```
# rpm -qa 'javajdk*'
javajdk-1.8.0u144-6691.el7.x86_64
```
If you have a HA datanode that runs the watchtower database, skip directly to Step 10 to update watchtower database
Enable and start the services that were reinstalled
```
systemctl enable mariadb
systemctl start mariadb
```
Upgrade MySQL
```
mysql_upgrade
```
The mysql_upgrade step may detect errors that trigger messages such as the following message (note: this example is from the Abiquo database server).
kinton_accounting.ACCOUNT_PERIOD_USAGE_VW Error : Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 100129, now running 100410. Please use mysql_upgrade to fix this error
These messages are expected and this same mysql_upgrade process will automatically fix these errors in its next stages.
Check that the mysql_upgrade process completes correctly.

Update the Abiquo Watchtower database

watchtower-db [-h DB hostname] [-P DB port] [-u user] [-p password] update

14. Upgrade steps from 4.7.x to 5.0.x

Start with your original version and perform the steps to the final version.

Click for Upgrade steps from 4.7.x to 5.0.x

Run Redis database script

On each Remote Services server:

# cd /usr/share/doc/abiquo-redis/redis/
# bash ./4.2.3/00-old-vsm-definitions.sh

Post-upgrade steps:

Change the tutorials' softlinks in the frontend servers. If there is a softlink /var/www/html/ui/config/tutorials pointing to /opt/abiquo/config/tutorials, change it to point to /opt/abiquo/tutorials instead.
If your Apache redirect addresses end in trailing slash characters ("/"), remove the trailing slashes

15. Upgrade steps from 5.0.x to 5.1.x

Start with your original version and perform the steps to the final version.

Click for Upgrade steps from 5.0.x to 5.1.x for Veeam

Run script to update job names on Veeam server

When upgrading from 5.0.x or 5.1.x to 5.1.2 or above, if you are using Veeam, run the following application that will update the job names on the Veeam server to allow duplicate VM names.

The instructions for running the tool are in the following file.

/usr/share/doc/abiquo-model/scripts/veeam-job-modifier/README.md

To run the tool, do these steps:

Edit the veeam.properties file and set the MySQL jdbc properties. Replace the examples with the values for the Abiquo database

abiquo.database.jdbcurl = jdbc:mysql://abiquoserver.example.com:3306/kinton
abiquo.database.user = mysqlUser
abiquo.database.password = mysqlPassword

Obtain the Veeam version and credentials to pass as arguments to the script
- veeam95u4 Run for usage with Veeam server 9.5u4 or veeam10 Run for usage with Veeam server 10
- -ip IP address of Veeam server
- -u, --user veeamServerUser
- -p, --password veeamServerPassword
The other argument defines a dry-run mode to test the script
- -no-dry, --no-dry-run If true, update Veeam job names. If false, only show what will the names will look like after the change

Run the tool in dry-run mode (with the argument "--no-dry-run false" and check the Veeam jobs that it will update.

java -jar /usr/share/doc/abiquo-model/scripts/veeam-job-modifier/veeam-job-modifier-jar-with-dependencies.jar veeam10 -ip \ http://veeamserver.example.com:9399/api -u veeamServerUser -p veeamServerPassword -no-dry false

Run the tool in production mode to update the Veeam server

java -jar /usr/share/doc/abiquo-model/scripts/veeam-job-modifier/veeam-job-modifier-jar-with-dependencies.jar veeam10 -ip \ http://veeamserver.example.com:9399/api -u veeamServerUser -p veeamServerPassword -no-dry true

After you run the tool, edit the veeam.properties file, and remove the temporary properties with the database credentials.

Click for Upgrade steps from 5.0.x to 5.1.2 or 5.2.x for VM names

Run mandatory database scripts on Redis database and Watchtower SQL database

When upgrading from any version lower than 5.1.2, do the following steps once (e.g. during upgrade to 5.1.2 OR upgrade to 5.2.x)

On the Abiquo Server, run the following tool that will generate two scripts to run on the Redis database and Watchtower SQL database.

These scripts change the use of the Abiquo VM Identifier (name attribute) as the UID to the ID of the VM as the new UID.

The instructions for running the tool are in the following file:

/usr/share/doc/abiquo-model/scripts/wt-db-redis-db-migration-tool/README.md

To run the tool and scripts, do these steps:

On the Abiquo Server, run the tool to generate the scripts, supplying the database credentials
```
$ java -jar /usr/share/doc/abiquo-model/scripts/wt-db-redis-db-migration-tool/wtrtool.jar \
 --kinton "jdbc:mysql://localhost:3306/kinton?autoReconnect=true&user=mysqlUser&password=mysqlPassword" \
 --output .
```
You should find the following scripts in the output directory (by default the current directory)
- redisdelta, which is Bash script
- watchtowerdelta.sql
For each Remote Services server, copy the redisdelta Bash script to the server.
On each Remote Services server, run the Bash script. Note that this script requires Bash version 4, which is the default version on Abiquo servers
```
bash ./redisdelta
```
Copy the SQL script to the Watchtower Monitoring Server.

Run the SQL script

mysql watchtower < ./watchtowerdelta.sql

Run Redis database script

On each Remote Services server:

# cd /usr/share/doc/abiquo-redis/redis/
# bash ./4.2.3/00-old-vsm-definitions.sh

16. Upgrade steps from 5.1.x to 5.2.x

Start with your original version and perform the steps to the final version.

When upgrading from 5.1.0 or 5.1.1 to 5.1.2 or above, follow the steps from the Upgrade steps from 5.0.x to 5.1.x block.

Click for Upgrade steps from 5.1.x to 5.2.x for Azure

Run Redis Script to update Azure VSM subscriptions

If you have VMs deployed in Azure, on the Remote Services server, run this script that will use the Redis address and port configured in abiquo.properties. The script will add the VM's Resource Group to the VSM Redis subscription of the VM. We assume that VMs are in the same Resource Group as their virtual datacenter. This is certainly true if the VMs were deployed from Abiquo. In any case, if you previously onboarded a VM in a different RG, the virtual machine definition synchronization process will update it. This script gets the resource group from the VDC provider ID with the format resourceGroup/vdcproviderId, e.g. abiquo-westeurope/abqvnet-vdcname.

First run the tool in dry-run mode and check the VMs to update

java -jar /usr/share/doc/abiquo-model/scripts/azure-resourcegroup-migration-tool/vm-resourcegroup.jar

Run the tool in production mode to update the subscriptions

java -jar /usr/share/doc/abiquo-model/scripts/azure-resourcegroup-migration-tool/vm-resourcegroup.jar -no-dry="true"

Click for Upgrade steps from 5.1.x to 5.2.x for Tomcat (step 3 is mandatory)

Configure HTTPS TLS between Tomcat servers

If you are using HTTPS TLS between the Tomcat servers, do these steps. For details of this configuration, see Configure Abiquo Tomcat with HTTPS for Remote RS.

On each Tomcat server (API and RS), restore the backup of the server.xml files from before the upgrade

Edit the server.xml files and add the new secretRequired="false" option to the HTTPS connector

<Service name="Catalina">

        <Connector
           protocol="org.apache.coyote.http11.Http11NioProtocol"
           port="8009" maxThreads="200"
           scheme="https" secure="true" SSLEnabled="true"
           keystoreFile="/opt/abiquo/tomcat/conf/remoters.jks" keystorePass="changeit" keyAlias="myremoters.bcn.abiquo.com"
           clientAuth="false" secretRequired="false"
           sslProtocol="TLS"/>

If you have a separate API and UI server, on the API server, edit the server.xml file and allow the AJP connector to listen everywhere, not just on localhost, by setting address="0.0.0.0". Also add secretRequired="false".

<Connector port="8010" protocol="AJP/1.3"
               enableLookups="false"
               tomcatAuthentication="false"
               connectionTimeout="20000"
               secretRequired="false"
               address="0.0.0.0"
               />

Click for Upgrade steps from 5.1.x to 5.2.x for Redis

Run Redis database script

These scripts can always be found on the Abiquo Server.

On each Remote Services server (including Monolithic sever) or Datanode server run the Redis scripts.

# cd /usr/share/doc/abiquo-redis/redis/
# bash ./4.2.3/00-old-vsm-definitions.sh

Click for Upgrade steps from 5.1.x to 5.2.x for billing dashboards

Remove deprecated billing dashboard scripts

In Abiquo 5.2, the billing dashboard feature has been integrated into the Abiquo platform.
The upgrade process will migrate most of the enterprise properties for billing scripts, which will make the old billing dashboard scripts invalid.

If you were using the billing dashboard in a previous version, do these steps.

To prevent errors, before the upgrade, you should have disabled the old billing dashboard scripts by removing the old cron jobs. If not, disable them now. see Upgrade billing dashboards
In Abiquo, upgrade enterprise properties to ensure valid billing data is displayed. See Upgrade billing dashboards
After you complete the upgrade, remove scripts and data. See Remove deprecated billing dashboard configuration

17. Upgrade steps for 5.2 versions

These steps apply to upgrades starting from version 5.2.0 and above.

Click here to show/hide the steps to upgrade 5.2 versions

Abiquo 5.2.0 or later to latest 5.2.x version

Run Redis database script
These scripts can always be found on the Abiquo Server.
On each Remote Services server (including Monolithic sever) or Datanode server run the Redis scripts
```
# cd /usr/share/doc/abiquo-redis/redis/
# bash ./4.2.3/00-old-vsm-definitions.sh
```

18. Configure Abiquo after the upgrade

Before you start the Abiquo tomcat server, add Abiquo configuration properties to the abiquo.properties file.
By default the abiquo.properties file is found in the /opt/abiquo/config/ folder.
See Changes to Abiquo configuration properties
Configure the user interface. The default UI location is /var/www/html/ui.
Optional: Add custom labels and translations in the lang_xx_XX_custom.json files in the lang folder
Add custom configuration to client-config-custom.json. See Configure Abiquo UI
If your API is not in the same domain as the UI, set the API endpoint pointing to your Abiquo API server:
```
{
    "config.endpoint": "http://myAPIserver/api"
}
```
Reporting changes: To upgrade the Abiquo Reports database for the upgrade to Abiquo 4.7.x+, contact Abiquo Support for the file and procedure.

19. Start Abiquo servers and services

To start the Abiquo platform servers and services, do these steps:

On the Abiquo server, restart the HTTP daemon to refresh the user interface files, and bring up the Tomcat server.
```
service httpd start
service abiquo-tomcat start
```
On the remote services server, start the Tomcat server
```
service abiquo-tomcat start
```
On the monitoring server: edit the file /opt/kairosdb/conf/kairosdb.properties to update the name of this variable and to remove the port from it:
- Replace the line kairosdb.datastore.cassandra.host_list=192.168.888.999:9160 .
- With this line kairosdb.datastore.cassandra.cql_host_list=192.168.888.999 . Please note the new cql_ preffix for this property.

On the monitoring server: edit the file /etc/cassandra/conf/cassandra.yml OR /etc/cassandra/default.conf/cassandra.yaml (whichever exists) to remove a variable:
- Remove the line starting with kairosdb.datastore.cassandra.datapoint_ttl and save and close the file.

On the monitoring server: edit the file /opt/kairosdb/conf/kairosdb.properties to add a new variable (ref: Internal JIRA SUP-333):
- kairosdb.datastore.cassandra.datapoint_ttl = 15768000

On the monitoring server: start the Cassandra service
```
sudo service cassandra start
```
WAIT about 5 minutes until the service is up and running
Start the KairosDB service
```
sudo service kairosdb start
```

Start the other services in this order

sudo service abiquo-emmett start
sudo service abiquo-delorean start

On the V2V server: restart the Tomcat server:
```
service abiquo-tomcat restart
```