Standard Abiquo minor or patch version update

To prepare your upgrade document, you can use these upgrade docs per installation profile:

1. Prevent cloud users from performing VM operations

In the UI in the Infrastructure view, select each physical machine and click Disable. 
Or using the API, set the state of each physical machine to DISABLED

2. Check for operations in progress on the platform

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

1. On the Abiquo Monolithic Server, Abiquo Server or Datanode server, check that the Abiquo RabbitMQ queues are empty.

   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.

    

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

3. Stop platform services for minor upgrade

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

To stop platform services:

1. Stop the API on the API server or Monolithic server

2. Stop the UI on the API server or Monolithic server or dedicated UI server

3. Stop Remote services server 

4. On the V2V Server you do not need to stop anything because the BPM remote service is run on-demand only

5. Stop Monitoring server

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

4. Make snapshots and backups of all platform servers

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

5. Prepare yum repositories on all servers

1. Check that you have the repository URL and credentials

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

3. 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 https://www.oreilly.com/library/view/learning-the-bash/1565923472/ch01s09.html

4. Clean yum and make cache

5. If you did not make snapshots of all servers already, then you could do this now.

6. 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. If your upgrade process goes through Abiquo 6.1.2, on all Remote Services servers (not V2V servers), Upgrade Guacamole server

   4. On the V2V server, check the /etc/sysconfig/abiquo/ec2-api-tools file exists.

       

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

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

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

    

8. Upgrade additional elements

For each upgrade, run the Redis database script to remove old VSM definitions, which can be found in the 4.2.3 subfolder.

By default, the upgrade scripts are on the Abiquo Server in the folder: /usr/share/doc/abiquo-redis/redis/

On each Remote Services server (including Monolithic sever) or Datanode server, run the Redis scripts

9. Upgrade additional services

If you are using an Abiquo service customization that is not distributed with OS packages, then please update it now before starting the services again.

10. Configure Abiquo after the upgrade

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

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 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:

    

3. SAML: If you are using SAML with multiple IDPs, restore the configuration as described at Restore SAML security beans after upgrade.

11. 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 and V2V server, start the Tomcat server

• On the Monitoring server, start the Cassandra service

• WAIT about 5 minutes until the service is up and running

• Start the KairosDB service and wait 1 minute

• Start the other services in this order