Skip to end of banner Go to start of banner

Upgrade Abiquo HA platform to v5.2.x

Skip to end of metadata

Created by MS, last modified on Apr 13, 2021

Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

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.

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

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

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

3. Check for operations in progress on the platform

Before you shut down the platform servers you should check that no operations are in progress.

4. Stop platform services

5. 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 Prepare to Upgrade Abiquo.

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 Upgrade Tomcat 8 to Tomcat 9 with HTTPS-SSL.

6. Disable old billing dashboard scripts

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 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.
```
# rm /etc/cron.d/abiquo-billing-ec2
# rm /etc/cron.d/abiquo-billing-arm
```

7. Prepare yum repositories on all servers

Unable to render {include} The included page could not be found.

8. Upgrade Datanode servers in HA

Unable to render {include} The included page could not be found.

9. Upgrade UI servers in HA

Unable to render {include} The included page could not be found.

10. Upgrade load balanced API servers in HA

Unable to render {include} The included page could not be found.

11. Upgrade Remote Services servers

Unable to render {include} The included page could not be found.

12. Upgrade Monitoring server

Unable to render {include} The included page could not be found.

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

Unable to render {include} The included page could not be found.

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

Unable to render {include} The included page could not be found.

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

Unable to render {include} The included page could not be found.

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

Unable to render {include} The included page could not be found.

Click for Upgrade steps from 5.1.x to 5.2.x for Tomcat with SSL

Unable to render {include} The included page could not be found.

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

Unable to render {include} The included page could not be found.

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

Unable to render {include} The included page could not be found.

16. 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 Properties
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 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:
```
{
    "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.

17. Start Abiquo servers and services

To start the Abiquo platform servers and services, do these steps:

On the Abiquo server, restart the HTTP daemon to refresh the user interface files, and bring up the Tomcat server.
```
service httpd start
service abiquo-tomcat start
```
On the Remote services server, start the Tomcat server
```
service abiquo-tomcat start
```
On the Monitoring server do these steps.
1. Edit the file /opt/kairosdb/conf/kairosdb.properties to update the name of the following variable and to remove the port from it:
  1. Replace the line kairosdb.datastore.cassandra.host_list=192.168.888.999:9160.
  2. With this line kairosdb.datastore.cassandra.cql_host_list=192.168.888.999. Please note the new cql_ prefix for host_list.
2. Edit the file /etc/cassandra/conf/cassandra.yml OR /etc/cassandra/default.conf/cassandra.yaml (whichever exists) to remove a variable:
  1. Remove the line starting with kairosdb.datastore.cassandra.datapoint_ttl and save and close the file.
3. Edit the file /opt/kairosdb/conf/kairosdb.properties to add a new variable (ref: Internal JIRA SUP-333):
  1. Add kairosdb.datastore.cassandra.datapoint_ttl = 15768000
On the Monitoring server, start the Cassandra service
```
sudo service cassandra start
```
WAIT about 5 minutes until the service is up and running
Start the KairosDB service
```
sudo service kairosdb start
```

Start the other services in this order

sudo service abiquo-emmett start
sudo service abiquo-delorean start

On the V2V server: restart the Tomcat server:
```
service abiquo-tomcat restart
```
In Abiquo, re-enable the physical machines!
Clear your browser cache to prevent glitches in the UI

No labels

Copyright © 2006-2024, Abiquo Holdings SL. All rights reserved