| Excerpt | ||
|---|---|---|
| ||
Upgrade or update your Abiquo hybrid cloud platform.
|
This section describes how to upgrade from Abiquo 5.2.0 or above to an Abiquo 5.4.x version.
- To upgrade from earlier versions, first see Upgrade Abiquo from 4.7 to 5.2.x
For your convenience, we have also prepared the following concise upgrade document that groups the commands by servers. However, we encourage you to use this Upgrade Abiquo document as your main reference, especially for the provider ID migration:
Please contact Abiquo Support for further information.
Minor version upgrade table
...
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 from 4.7 to 5.2.x There is no upgrade path from NSX-V to NSX-T because VMware does not support this upgrade |
| Note |
|---|
|
| 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 |
|---|
...
| start-numbering-at | h2 |
|---|
Prevent cloud users from performing VM operations
- 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.
...
Unmount the previous shared folder if you have it mounted:
...
Update Abiquo packages:
Mount again the shared folder from the second step.
...
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.
...
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
...
To upgrade the Abiquo Watchtower database, on the monitoring appliance, run the command below:
...
- 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.
...
Configure Abiquo after the upgrade
...
Reporting changes: To upgrade the Abiquo Reports Server for the upgrade to Abiquo 5.3.x, contact Abiquo Support.
...
| Include Page | ||||
|---|---|---|---|---|
|