Page Comparison

Prepare branding

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

Backup SAML multiple IdP files

• Always back up these files:
  1. From every API server:
     
     1. sudo 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)
  2. From every UI server:
     

     1. sudo cp /var/www/html/ui/config/client-config-custom.json /var/www/html/ui/config/client-config-custom.json_$(date +%Y%m%d_%H%M%S).log

     2. sudo cp --recursive /var/www/html/ui/lang /var/www/html/ui/lang_$(date +%Y%m%d_%H%M%S)

Prevent cloud users from performing VM operations

1. In the UI in the Infrastructure view, select each physical machine and click Disable
2. 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.

Stop platform services

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.

It may also be convenient to make a quick backup of all important system data. For more details, see .

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.

1. On the server where you were running the billing packages, remove the Cron jobs to run the billing scripts.

   
   

2. Delete the last bills from the previous version of the billing dashboards (from the billing_consolidation and 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.

Prepare yum repositories on all servers

Upgrade Distributed API and DB servers

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

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

Upgrade Remote Services servers

Upgrade Monitoring server

Upgrade steps from 4.7.x to 5.0.x

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

Upgrade steps from 5.0.x to 5.1.x

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

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 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  to the abiquo.properties file.
   By default the abiquo.properties file is found in the /opt/abiquo/config/ folder.
   See

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
   If your API is not in the same domain as the UI, set the API endpoint pointing to your Abiquo API server:

   
   

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