Page Comparison

...

Prepare yum repositories on all servers

Prepare yum repositories on all servers for v5.2

...

Upgrade distributed API and DB servers

This section describes the upgrade for a standard API and DB server.

These steps are for a Distributed API Server with the database on the API server.

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

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

After the update, check versions.

Check that the symbolic link to the latest version of Java points to Java 11 on Monolithic Server or Datanode

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

Check that the correct Tomcat version will be used on the Monolithic Server

# 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 Monolithic 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

...

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

• OR To upgrade to a version with patch number that is not zero, for example, version 5.2.1, enable both repositories:

  Code Block
  yum-config-manager --enable abiquo-base yum-config-manager --enable abiquo-updates

• Optionally add your username and password to the Abiquo repos

  Code Block
  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

...

Upgrade distributed API and DB servers

This section describes the upgrade for a standard API and DB server.

These steps are for a Distributed API Server with the database on the API server.

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

1. Remove the Erlang and Galera packages.

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

2. Install new RabbitMQ and MariaDB server

   Code Block
   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

3. Upgrade Abiquo to 5.2.x

   Code Block
   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

4. After the update, check versions.

   Check that the symbolic link to the latest version of Java points to Java 11 on Monolithic Server or Datanode

   Code Block
   # cd /usr/java # ll latest -> /usr/java/jdk-11.0.6+10/lib/security

   Check that the correct Tomcat version will be used on the Monolithic Server

   Code Block
   # cd /opt/abiquo/tomcat/bin # keytool -list -keystore cacerts -alias (hostname or fqdn)

   For example

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

   Enable and start the new services

   Code Block
   systemctl enable mariadb systemctl enable rabbitmq-server systemctl start mariadb systemctl start rabbitmq-server

   Upgrade MySQL

   Code Block
   mysql_upgrade

   The mysql_upgrade step may detect errors that trigger messages such as the following:

   Code Block
   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.

5. Check that your hostname is in your DNS or in your /etc/hosts file

Upgrade the Abiquo API databases

Code Block
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: 

Code Block
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

Clear the database checksums

Code Block
abiquo-db clearCheckSums

6. Retry the above abiquo-db update command.

Change file owners to tomcat user

Code Block
chown -R tomcat /opt/abiquo

This section contains an alternative upgrade procedure for standalone Database servers and a Distributed API server without DB

...

Upgrade standalone database servers

This step is for standalone MariaDB database servers.

Abiquo will upgrade to a new version of MySQL that requires a manual upgrade path of dependencies.

...

Remove the Galera package

yum remove galera
yum clean all && yum makecache

...

Install new MariaDB server

yum install MariaDB-server

Before you confirm, check that the packages will be installed from the abiquo-base repository

1. 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

After the update, 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

Enable 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:

...

1. 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 Monolithic 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

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

   For example

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

2. Enable and start the new services

   Code Block
   systemctl enable mariadb systemctl enable rabbitmq-server systemctl start mariadb systemctl start rabbitmq-server

3. Upgrade MySQL

   Code Block
   mysql_upgrade

   The mysql_upgrade step may detect errors that trigger messages such as the following:

   Code Block
   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.

4. Check that your hostname is in your DNS or in your /etc/hosts file

5. Upgrade the Abiquo API databases

...

1. Code Block
   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: 

   Code Block
   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

      Code Block
      abiquo-db clearCheckSums

   2. Retry the above abiquo-db update command.

2. Change file owners to tomcat user

   Code Block
   chown -R tomcat /opt/abiquo

This section contains an alternative upgrade procedure for standalone Database servers and a Distributed API server without DB

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

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

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

Upgrade steps from 4.7.x to 5.0.x

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

...

Run Redis database scriptUpgrade steps from 4.7.x to 5.0.x

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

Upgrade steps from 5.0.x to 5.1.x

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

...

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.

...

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

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.

...

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.

1. On the remote services servers, upgrade Abiquo to 5.2.x

   Code Block
   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

2. After the update, check versions of Java and Tomcat

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

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

   Check that the correct Tomcat version will be used

   Code Block

   # 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

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

   For example

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

3. On all remote services servers using SSL

   Edit the Tomcat server configuration file:

   Code Block
   /opt/abiquo/tomcat/conf/server.xml

   Find the location of the certificate files for Java 8

   Code Block
   keystoreFile="/usr/java/default/jre/lib/security/cacerts"

   Change it to the location for Java 11 (e.g. remove "/jre")

   Code Block
   keystoreFile="/usr/java/default/lib/security/cacerts"

4. On all remote services servers, change file owners to tomcat user

   Code Block
   chown -R tomcat /opt/abiquo

5. 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

   Code Block
   chown -R tomcat /opt/vm_repository chmod -R a+r /opt/vm_repository

   
   

...

Upgrade monitoring server

This step is for Watchtower monitoring servers in all installations.

1. 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

   Code Block
   rpm -e --nodeps jdk

2. Check the jdk to install is version 8

   Code Block
   rpm -qa | grep jdk

3. Check that Java is correctly installed:

   1. If you execute this command and get that error, please execute the command from the next bullet:

      Code Block
      $ java -bash: java: command not found

   2. 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)":

      Code Block
      $ 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

4. As for the Abiquo DB steps, remove Galera, which will also remove MariaDB

   Code Block
   yum remove galera

5. Clean yum and make cache

   Code Block
   yum clean all && yum makecache

6. Install MariaDB

   Code Block
   yum install MariaDB-server

7. Update Abiquo

   Code Block
   yum update

8. Check that the Java package is now "javajdk" to use Java 1.8.0u144 with Cassandra:

   Code Block
   # rpm -qa 'javajdk*' javajdk-1.8.0u144-6691.el7.x86_64

9. If you have a HA datanode that runs the watchtower database, skip directly to Step 10 to update watchtower database

10. Enable and start the services that were reinstalled

    Code Block
    systemctl enable mariadb systemctl start mariadb

11. Upgrade MySQL

    Code Block
    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).

    Code Block
    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.

12. Update the Abiquo Watchtower database

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

13. Edit the file /opt/kairosdb/conf/kairosdb.properties to update the name of the following variable and to remove the port from it:

    1. Remove the line kairosdb.datastore.cassandra.host_list=192.168.888.999:9160.
       And add this line kairosdb.datastore.cassandra.cql_host_list=192.168.888.999.
       Please note the new cql_ prefix for host_list

    2. Add kairosdb.datastore.cassandra.datapoint_ttl = 15768000 (ref: Internal JIRA SUP-333):

14. Edit the file /etc/cassandra/conf/cassandra.yml OR /etc/cassandra/default.conf/cassandra.yaml (whichever exists) to remove a variable:

    1. Remove the line starting with kairosdb.datastore.cassandra.datapoint_ttl and save and close the file.

...

Upgrade steps from 4.7.x to 5.0.x

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

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

...

Upgrade steps from 5.0.x to 5.1.x

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

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.

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

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

<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"
               />

Upgrade steps for 5.2 versions

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

...

Upgrade steps for 5.2 versions

...

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.

Start Abiquo servers and services

Start Abiquo servers and services

...

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

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

...

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.

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

Upgrade steps for 5.2 versions

These steps apply to upgrades starting from version 5.2.0 and above

...

Configure Abiquo after the upgrade

1. 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

2. 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:

   Code Block
   { "config.endpoint": "http://myAPIserver/api" }

   
   

3. Reporting changes: To upgrade the Abiquo Reports database for the upgrade to Abiquo 4.7.x+, contact Abiquo Support for the file and procedure.

...

Start Abiquo servers and services

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

1. On the Abiquo server, restart the HTTP daemon to refresh the user interface files, and bring up the Tomcat server.

   Code Block
   service httpd start service abiquo-tomcat start

2. On the Remote services server, start the Tomcat server

   Code Block
   service abiquo-tomcat start

3. On the Monitoring server do these steps.

   1. Edit the file /opt/kairosdb/conf/kairosdb.properties to update the name of the following variable and to remove the port from it:

      1. Replace the line kairosdb.datastore.cassandra.host_list=192.168.888.999:9160.

      2. With this line kairosdb.datastore.cassandra.cql_host_list=192.168.888.999. Please note the new cql_ prefix for host_list.

   2. Edit the file /etc/cassandra/conf/cassandra.yml OR /etc/cassandra/default.conf/cassandra.yaml (whichever exists) to remove a variable:

      1. Remove the line starting with kairosdb.datastore.cassandra.datapoint_ttl and save and close the file.

   3. Edit the file /opt/kairosdb/conf/kairosdb.properties to add a new variable (ref: Internal JIRA SUP-333):

      1. Add kairosdb.datastore.cassandra.datapoint_ttl = 15768000

4. On the Monitoring server, start the Cassandra service

   Code Block
   sudo service cassandra start

5. WAIT about 5 minutes until the service is up and running

6. Start the KairosDB service

   Code Block
   sudo service kairosdb start

7. Start the other services in this order

   Code Block
   sudo service abiquo-emmett start sudo service abiquo-delorean start

8. On the V2V server: restart the Tomcat server:

   Code Block
   service abiquo-tomcat restart

9. In Abiquo, re-enable the physical machines!

10. Clear your browser cache to prevent glitches in the UI