Versions Compared

Key

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


Table of Contents

 

...

start-numbering-ath2

Upgrade versions

This section describes how to upgrade from Abiquo 5.2.0 or above to an Abiquo 5.4.x version. 

Please contact Abiquo Support for further information.

Minor version upgrade table

From versionTo versionUpgrade typeNotes
5.4.05.4.1StandardSee Standard Abiquo minor or patch version update
5.4.15.4.2StandardSee Standard Abiquo minor or patch version update


Warnings and notices

Warning

Abiquo YUM repositories are no longer open, please contact Abiquo Support to obtain your credentials

This upgrade process starts from Abiquo 5.2.0 or above. To upgrade from earlier versions, please see Upgrade Abiquo

There is no upgrade path from NSX-V to NSX-T because VMware does not support this upgrade


Note
  • The upgrade will overwrite lang_en_US.json. If you have customized labels or translations, back them up before the upgrade and restore them afterwards accordingly.
  • The upgrade will overwrite the SAML login configuration for multiple IdPs. If you use SAML with multiple IdPs, back up the configuration files before the upgrade and add the multiple IdPs afterwards accordingly. See Restore SAML security beans after upgrade


Warning

The upgrade to Abiquo 5.3 includes a migration to provider ID as the identifier of a deployed VM.

See Provider ID as VM identifier upgrade

Prepare the provider ID migration before your upgrade. See Create a test VM and run PIM planner on a database dump


Table of contents

Table of Contents

 

Numberedheadings
start-numbering-ath2

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.



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


Upgrade packages on ALL servers

These instructions are for monolithic, distributed, and HA environments.

  1. Update Abiquo packages:


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

    1. On Abiquo Server and Remote Services


    2. On the Remote Services with Appliance Manager and the V2V Server (i.e. servers that mount the NFS repository)


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

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

  2. Upgrade the Abiquo API databases


    If the liquibase update fails with a message similar to the following: 

    Do the following steps

    1. Clear the database checksums


    2. Retry the above abiquo-db update command.


  3. To upgrade the Abiquo Watchtower database, on the monitoring appliance, run the command below:


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

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

  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. SAML: If you are using SAML with multiple IDPs, restore the configuration as described at .

  4. Reporting changes: To upgrade the Abiquo Reports Server for the upgrade to Abiquo 5.3.x, contact Abiquo Support.

Start Abiquo server and services

...