Versions Compared

Version Old Version 24 New Version Current
Changes made by

MS

MS

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

Table of Contents

Prerequisites

...

Code Block
yum update 'abiquo-*' && yum update jdk

Update databases

Info

This step must be done on the database server.

...

Info

There is a known issue with upgrades from 3.2 versions where the following message appears and the liquibase update fails: 

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

This can be easily solved by executing the following command and retrying the abiquo-liquibase update command.

Code Block
abiquo-liquibase clearCheckSums

 

Additional

...

steps for intermediate versions

...

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

Info

All scripts are located on the Abiquo Server.

Expand
titleStart here if you are upgrading from Abiquo 3.0

In 3.1 we introduced credentials encryption, so you will need to encryption.

First install the new encryption libraries for Java 8

Upgrade from Abiquo 3.1.x to 3.2.x

To cypher your current credentials. Please , please follow these instructions:

Upgrade from Abiquo 3.0.1 to 3.1

Now continue with the sections for the following 3.x versions

Expand
titleStart here if you are upgrading from Abiquo 3.1

If you are upgrading from 3.1, Abiquo 3.2 requires a new Java Cryptography Extension (JCE) libraries for Java 8 so you will need to install the new encryption libraries.

Upgrade from Abiquo 3.1.x to 3.2.x

You must apply this script to the Remote Services Redis database:

Upgrade from Abiquo 3.1.x to 3.2.x

Upgrade redis schema

Execute the Redis delta script on each Abiquo Server running Redis (Abiquo Server and Abiquo RS nodes) to update the schema to the 3.2 version. This script can be found on following path on the Abiquo Server

Code Block
/usr/share/doc/abiquo-server/redis/3.2.0/redis-delta-3.0_to_3.2.py

And in the next path in the Abiquo Remote services

Code Block
/usr/share/doc/abiquo-remote-services/redis/3.2.0/redis-delta-3.0_to_3.2.py

Now continue with the sections for the following 3.x versions

Expand
titleStart here if you are upgrading from Abiquo 3.2

Execute this script on the Abiquo Management Server:Upgrade from Abiquo 3.2.x to 3.4

Code Block
/usr/share/doc/abiquo-server/redis/3.4.0/00-failed-templates.sh

And this other script on the Abiquo Remote Services:Upgrade from Abiquo 3.2.x to 3.4

Code Block
/usr/share/doc/abiquo-remote-services/redis/3.4.0/01-old-vsm-definitions.sh

Now continue with the sections for the following 3.x versions

Expand
titleStart here if you are upgrading from Abiquo 3.4

Execute this script on the Abiquo Management Server:Upgrade from Abiquo 3.4.x to 3.6

Code Block
yum -y install python-redis
python /usr/share/doc/abiquo-server/redis/3.6.0/02-null-creation-timestamp.py

And this other script on the Abiquo Remote Services:

Code Block
Upgrade from Abiquo 3.4.x to 3.6
yum -y install python-redis
/usr/share/doc/abiquo-server/redis/3.6.0/00-old-vsm-definitions.sh
python /usr/share/doc/abiquo-remote-services/redis/3.6.0/01-vdc-provider-id.py
Expand
titleUpgrade to Abiquo 3.6.x

Execute this script on the Abiquo Remote Services:

Code Block
python /usr/share/doc/abiquo-remote-services/redis/3.6.2/00-digitalocean-v2.py

Configuration

Add Abiquo Configuration Properties to the abiquo.properties file as required.

UI configuration

After the upgrade is complete, perform the UI configuration. The default UI location in Abiquo 3.x is /var/www/html/ui

  • 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

      • The essential UI configuration is the API endpoint pointing to your Abiquo API server

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