Upgrade Abiquo

1 1. Introduction
2 2. Warnings and notices
3 3. Prevent cloud users from performing VM operations
4 4. Check for operations in progress on the platform
5 5. Stop platform services
6 6. Back up the main platform elements
7 7. Make snapshots and backups of all platform servers
8 8. Prepare yum repositories for 6.0 or 6.0.x or 6.1 or 6.1.x
9 9. Upgrade packages on ALL servers
10 10. Update the Abiquo databases
11 11. Upgrade additional elements
12 12. Configure Abiquo after the upgrade
13 13. Start Abiquo server and services

1. Introduction

The upgrade to the latest version of Abiquo, see Upgrade Abiquo in the main Abiquo documentation space

This section describes how to upgrade from Abiquo 5.4.x or Abiquo 6.0.x to an Abiquo 6.1.x version.

To upgrade from earlier versions, first see:
- Upgrade Abiquo from 4.7 to 5.2.x
- Upgrade Abiquo from 5.2 to 5.4.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 the current Upgrade Abiquo document as your main reference:

Upgrade Abiquo 5.4 to 6.1.x distributed by servers
- This document is valid to upgrade from Abiquo 5.4.x or Abiquo 6.0.x to an Abiquo 6.1.x version

Please contact Abiquo Support for further information.

Major version upgrade table

From version	To version	Upgrade type	Notes

From version	To version	Upgrade type	Notes
5.4.x	6.0.x	Standard	Follow the process in this document (or at Upgrade Abiquo 5.4 to 6.0.x distributed by servers )
6.0.x	6.1.x	Standard	Follow the process in this document (or at Upgrade Abiquo 5.4 to 6.1.x distributed by servers ). + Deactivate on-premise billing until you are ready to switch and have billed the previous month

Minor version upgrade table

From version	To version	Upgrade type	Notes

From version	To version	Upgrade type	Notes
6.0.0	6.0.1	Standard	See Standard Abiquo minor or patch version update
6.0.1	6.0.2	Standard	See Standard Abiquo minor or patch version update
6.0.2	6.0.3	Standard	See Standard Abiquo minor or patch version update
6.0.3	6.0.4	Standard	See Standard Abiquo minor or patch version update
6.0.4	6.0.5	Standard	See Standard Abiquo minor or patch version update
6.0.5	6.0.6	Standard	See Standard Abiquo minor or patch version update
6.0.6	6.0.7	Standard	See Standard Abiquo minor or patch version update
6.0.7	6.0.8	Standard	See Standard Abiquo minor or patch version update
6.1.0	6.1.1	Standard	See Standard Abiquo minor or patch version update
6.1.1	6.1.2	Standard + Guacamole	See Standard Abiquo minor or patch version update and Upgrade Guacamole server
6.1.2	6.1.3	Standard	See Standard Abiquo minor or patch version update
6.1.3	6.1.4	Standard	See Standard Abiquo minor or patch version update

2. Warnings and notices

Before you begin, contact Abiquo Platform and Customer Success department to obtain your credentials because Abiquo YUM repositories require a login.
There is no upgrade path from NSX-V to NSX-T because VMware does not support this upgrade.
The upgrade will overwrite lang_en_US_labels.json. If you have customized labels or translations, back them up before the upgrade and restore them afterwards.

SAML upgrade

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.
For Abiquo 6.0.0+, you must configure the SAML maximum authentication age property or SAML will not initialize

Changes to enterprise properties for AWS billing

Before you upgrade to Abiquo 6.0.0, add the amazon_bucket_region as an enterprise property. The value is the code for the AWS region where your billing bucket is located (for example, us-east-1). This property applies to AWS resellers and standard accounts with billing dashboard configurations

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

4. Check for operations in progress on the platform

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

Check that the Abiquo RabbitMQ queues are empty on the Abiquo Monolithic Server, Abiquo Server or Datanode server
The number of messages in all queues must be 0.
# rabbitmqctl list_queues messages name

# rabbitmqctl list_queues messages name Listing queues ... 0 abiquo.am.notifications 0 abiquo.bpm.notifications 0 abiquo.datacenter.requests.ADatacenter.bpm 0 abiquo.datacenter.requests.ADatacenter.virtualfactory 0 abiquo.ha.tasks 0 abiquo.nodecollector.notifications 0 abiquo.pcrsync.messages 0 abiquo.pcrsync.parking-expect-no-consumers 0 abiquo.scheduler.fast.requests 0 abiquo.scheduler.requests 0 abiquo.scheduler.slow.requests 0 abiquo.tracer.traces 0 abiquo.virtualfactory.notifications 0 abiquo.virtualmachines.definitionsyncs 0 abiquo.vsm.eventsynk ...done.
On the V2V Server, check for any active conversions by checking for the V2V or Mechadora processes
$ ps aux | grep v2v $ ps aux | grep mechadora

When user VM operations are blocked and all of the above checks show that no tasks are running, it is safe to halt the platform.

5. Stop platform services

This section describes how to stop platform services on all servers.

To stop platform services:

Stop the API on the API server or monolithic server
Stop the UI on the API server or monolithic server or dedicated UI server
Stop remote services server
V2V Server
You do not need to stop anything because the BPM remote service is run on-demand only
Stop monitoring server
On the monitoring server, check if Cassandra is really dead
Get the process number for Cassandra (the first number in the output of the previous command), and kill it. In this example, Cassandra is process 12345.

All processes on platform servers should now be halted.

6. Back up the main platform elements

To perform a basic backup of the platform, run the following backups:

7. Make snapshots and backups of all platform servers

This is a major upgrade, so we recommend that you make a snapshot and/or a full backup of your platform servers.

8. Prepare yum repositories for 6.0 or 6.0.x or 6.1 or 6.1.x

Check that you have the repository URL and credentials

On all Abiquo Servers, such as Abiquo API, Remote Services, Watchtower monitoring.

Prepare yum repositories for 6.0.0 or 6.1.0

To upgrade to a version with a patch number of zero, for example, version 6.0.0 or version 6.1.0
1. Remove the previous version Abiquo release packages.
2. Find the abiquo-release-ee package for your version in the list of available versions
3. Install the release package.
  For Abiquo 6.1.0, the command would be similar to the following:
  For Abiquo 6.1.1, the release package would be:
4. For major versions, disable the updates repo. See 8.4.5. Adding, Enabling, and Disabling a Yum Repository | Red Hat Product Documentation

Prepare yum repositories for 6.0.x or 6.1.x

Check that you have the repository URL and credentials
To upgrade to the latest version with a patch number that is not zero, for example, version 6.0.x or version 6.1.x, enable both repositories:
Optionally add your username and password to the Abiquo repos
Don't forget to use a backslash to escape any shell special characters. For more details, see Learning the bash Shell, Second Edition
Clean yum and make cache
If you did not make snapshots of all servers already, then you could do this now.

9. Upgrade packages on ALL servers

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

Check in your RS server(s) if there is an NFS shared folder for the NARS results (related to the Abiquo configuration property abiquo.nars.async.fileresults.path):
Unmount the previous shared folder if you have it mounted:
Update Abiquo packages:
Mount the shared folder from the second step again.
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

10. 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
1. Clear the database checksums
2. Retry the above abiquo-db update command.
To upgrade the Abiquo Watchtower database, on the monitoring appliance, run the command below:
Reporting: The Abiquo reports server now runs with JasperReports v7.8.0

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

If you are using the Abiquo billing integration, to avoid issues with duplicate billing data, deactivate on-premise billing until after you bill for the previous month.

To deactivate on-premise billing:

Log in to the Abiquo database server as administrator
In MySQL, as an administrator, run the following command
update kinton.system_properties set value = 0 where name = "client.billing.onpremise.enabled";

When you are ready to activate on-premise billing, you can do this in the Abiquo UI, in Configuration view on the Billing tab. See Configure on premise billing

12. 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 and Changes to UI configuration
If your API is not in the same domain as the UI, set the API endpoint pointing to your Abiquo API server:
SAML: If you are using SAML with multiple IDPs, restore the configuration as described at Restore SAML security beans after upgrade.

13. Start Abiquo server 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.
On the Remote services server, start the Tomcat server
On the Monitoring server: edit the file /opt/kairosdb/conf/kairosdb.properties to update the name of this variable and to remove the port from it:
- Replace the line kairosdb.datastore.cassandra.host_list=192.168.888.999:9160.
- With this line: kairosdb.datastore.cassandra.cql_host_list=192.168.888.999. Please note the new cql_ prefix for this property.
On the Monitoring server: edit the file /etc/cassandra/conf/cassandra.yml OR /etc/cassandra/default.conf/cassandra.yaml (whichever exists) to remove a variable:
- Remove the line starting with kairosdb.datastore.cassandra.datapoint_ttl and save and close the file.
On the Monitoring server: edit the file /opt/kairosdb/conf/kairosdb.properties to add a new variable (our ref: Internal JIRA SUP-333):
- kairosdb.datastore.cassandra.datapoint_ttl = 15768000
On the Monitoring server: start the Cassandra service
WAIT about 5 minutes until the service is up and running
Start the KairosDB service
Start the other services in this order
On the V2V server: restart the Tomcat server:

Finally, in Abiquo, re-enable the physical machines!

After the upgrade, to prevent glitches in the UI, clear your browser cache