This section describes how to upgrade from Abiquo 4.7.0 or above to an Abiquo 5.2.x version. Please contact Abiquo Support for further information.
| Table of Contents | ||
|---|---|---|
|
| Warning | |
|---|---|
| title | Major upgradeThe 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 |
| Note |
|---|
|
Prepare branding
If you are upgrading from Abiquo 4.7.x, the new UI in Abiquo 5.0 requires new branding. See Abiquo branding guide
...
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
...
Check for operations in progress on the platform
| Include Page | ||||
|---|---|---|---|---|
|
...
Back up the main platform elements
Back up the main platform elements
| Include Page | ||||
|---|---|---|---|---|
|
| Note |
|---|
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. |
...
If you are using the billing dashboard scripts from previous versions, disable them and delete last bills before you continue with the upgrade.
On the server where you were running the billing packages, remove the Cron jobs to run the billing scripts.
Code Block # rm /etc/cron.d/abiquo-billing-ec2 # rm /etc/cron.d/abiquo-billing-armDelete the last bills from the previous version of the billing dashboards (from the kinton.billing_consolidation and kinton.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.
...
Stopplatform services
| Include Page | ||||
|---|---|---|---|---|
|
...
Make snapshots and backups of all platform servers
...
Prepare yum repositories on all servers for v5.2
| Include Page | ||||
|---|---|---|---|---|
|
...
Upgrade distributed API and DB servers
...
Upgrade Distributed API and DB server to v5.2
| Include Page | ||||
|---|---|---|---|---|
|
...
This section contains an alternative upgrade procedure for standalone Database servers and a Distributed API server without DB
...
| Expand | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
Upgrade standalone database servers Upgrade standalone Database servers to v5.2
Upgrade distributed API servers Upgrade Distributed API Server without DB to v5.2
|
...
Upgrade remote services servers
Upgrade remote services servers to v5.2
| Include Page | ||||
|---|---|---|---|---|
|
...
Upgrade monitoring server
Upgrade monitoring server to v5.2
| Include Page | ||||
|---|---|---|---|---|
|
...
Upgrade steps from 4.7.x to 5.0.x
...
| Expand | ||||||
|---|---|---|---|---|---|---|
| ||||||
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.
| Expand | ||||||
|---|---|---|---|---|---|---|
| ||||||
Upgrade steps from 5.0.x to 5.1.x for Veeam
|
| Expand | ||||||
|---|---|---|---|---|---|---|
| ||||||
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.
...
| Expand | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
| Expand | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
| Expand | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
| Expand | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
Upgrade steps for 5.2 versions
These steps apply to upgrades starting from version 5.2.0 and above.
...
| Expand | ||||||
|---|---|---|---|---|---|---|
| ||||||
Upgrade steps for 5.2 versions
|
...
Configure Abiquo after the upgrade
Before you start the Abiquo Tomcat server, add Abiquo configuration properties to the abiquo.properties file.
By default the abiquo.properties file is found in the /opt/abiquo/config/ folder.
See Changes to Abiquo configuration propertiesConfigure 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 Configure Abiquo UI
If your API is not in the same domain as the UI, set the API endpoint pointing to your Abiquo API server:Code Block { "config.endpoint": "http://myAPIserver/api" }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
Start Abiquo servers and services
| Include Page | ||||
|---|---|---|---|---|
|