Versions Compared

Old Version 27

changes.mady.by.user MS

Saved on

compared with

New Version 28

changes.mady.by.user MS

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


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.

Table of Contents
maxLevel2

 

Numberedheadings
start-numbering-ath2


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


Prepare branding

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



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.


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), see commands below. Remove the bills for Azure and Amazon providers, for the number of months covered by the abiquo.enterprise.property.billing.monthoffset system property, which has a default value of 2 months. Later the new billing dashboards feature will regenerate these bills:


Stop platform services



Back up the main platform elements


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 .



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.


Prepare yum repositories on all servers


Upgrade Monolithic server



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.

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



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


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



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


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


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


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


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



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