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
Check for operations in progress on the platform
Before you shut down the platform servers you should check that no operations are in progress.
Back up the main platform elements
Stop platform services
Make snapshots and backups of all platform servers
This is a major upgrade, so we recommend that you make a snapshot and/or a backup of your platform servers.
Prepare yum repositories for 5.4
Prepare yum repositories for 5.4.x
Upgrade packages on ALL servers
These instructions are for monolithic, distributed, and HA environments.
Check in your RS server(s) if there is an NFS shared folder for the NARS results (related to the abiquo.nars.async.fileresults.path):
bash
Unmount the previous shared folder if you have it mounted:
bash
Update Abiquo packages:
Mount again the shared folder from the second step.
bash
The Abiquo services must run as the tomcat user (not root), so set the required permissions and enforce the use of the package configuration files. If you have a MONOLITHIC SERVER do all of the following steps on the Monolithic server
On Abiquo Server and Remote Services
On the Remote Services with Appliance Manager and the V2V Server (i.e. servers that mount the NFS repository)
On the V2V server, check the /etc/sysconfig/abiquo/ec2-api-tools file exists. The file must contain the following configuration. If the file does not exist, create it and add this configuration.
For CentOS 7
Update the Abiquo databases
Check that your hostname is in your DNS or in your /etc/hosts file
Upgrade the Abiquo API databases
If the liquibase update fails with a message similar to the following:
Do the following steps
Clear the database checksums
Retry the above abiquo-db update command.
To upgrade the Abiquo Watchtower database, on the monitoring appliance, run the command below:
Reporting changes: To upgrade the Abiquo Reports Server for the upgrade to Abiquo 5.3.x, contact Abiquo Support for more information.
The Abiquo Reports Server now runs with JasperReports v7.8.0
Perform the provider ID migration in an upgrade through 5.3 only
For an upgrade that passes through Abiquo 5.3, perform the provider ID migration using the PIM tools.
Please note that the PIM migration tools use Java version 11.
Run the PIM planner
Run the PIM migrator
Upgrade additional elements
By default, you will find the upgrade scripts (e.g. for Redis definitions) on the Abiquo Server under the folder: /usr/share/doc/abiquo-redis/redis/
For each upgrade step, run the Redis database script to remove old VSM definitions, which can be found in the 4.2.3 subfolder
On Remote Services server:
If you have custom billing queries, please update them now.
Click here to show/hide the steps to upgrade from 5.2.0 or higher to 5.3.x
Click here to show/hide the steps to upgrade from 5.3.0 or higher to 5.4.x
Click here to show/hide the steps to upgrade from 5.4.0 or higher to 5.4.x
Configure Abiquo after the upgrade
Before you start the Abiquo tomcat server, add to the abiquo.properties file. By default the abiquo.properties file is found in the /opt/abiquo/config/ folder. See
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 If your API is not in the same domain as the UI, set the API endpoint pointing to your Abiquo API server:
SAML: If you are using SAML with multiple IDPs, restore the configuration as described at .
Reporting changes: To upgrade the Abiquo Reports Server for the upgrade to Abiquo 5.3.x, contact Abiquo Support.
Please note that the PIM migration tools use Java version 11.