Upgrade Abiquo from 5.2 to 5.4.x

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

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

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.

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

# On DB server, back up the Abiquo MySQL DBs
mysqldump --routines --triggers kinton            > kinton.sql-$(date +%Y%m%d_%H%M%S)
mysqldump --routines --triggers kinton_accounting > kinton_accounting.sql-$(date +%Y%m%d_%H%M%S)

# On the Monitoring server, back up Watchtower DB
mysqldump --routines --triggers watchtower            > watchtower.sql-$(date +%Y%m%d_%H%M%S)

# On the Abiquo API Server or UI server, back up the UI
tar cvfz /var/www/html/ui.tgz-$(date +%Y%m%d_%H%M%S) /var/www/html/ui

# If you are using SAML authentication with multiple IdPs, on ALL Abiquo API Servers, back up this file
cp 
/opt/abiquo/tomcat/webapps/api/WEB-INF/classes/springresources/security/saml/security-saml-generated-beans.xml /opt/abiquo/tomcat/webapps/api/WEB-INF/classes/springresources/security/saml/security-saml-generated-beans.xml-$(date
 +%Y%m%d_%H%M%S)

# On ALL servers, back up the /opt/abiquo folder
tar cvfz /opt/abiquo.tgz-$(date +%Y%m%d_%H%M%S) /opt/abiquo

# On Abiquo Monolithic or API Server, Remote Services, or Datanode, back up Redis
redis-cli save
cp -a /var/lib/redis /var/lib/redis-$(date +%Y%m%d_%H%M%S)

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

   systemctl stop abiquo-tomcat

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

   systemctl stop httpd

3. Stop remote services server

   systemctl stop abiquo-tomcat

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

5. Stop monitoring server

   systemctl stop abiquo-delorean
   systemctl stop abiquo-emmett
   systemctl stop kairosdb
   systemctl stop cassandra

6. On the monitoring server, check if Cassandra is really dead

   ps auwx | grep cassandra

   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.

   kill -9 12345

All processes on platform servers should now have halted.

The PIM planner connects to the Abiquo kinton database and extracts the data for the PIM migrator tool.

• The PIM planner will process each deployed VM to:

  • Compute the provider ID

  • Define the rename of any backup jobs or groups

  • Define the rename of any firewalls and load balancers

The PIM planner doesn't make any changes to the platform but you must run it after you upgrade the database to Abiquo 5.3.

What is the output of the PIM planner?

• A log in standard output (you should redirect it to a file)

• A migration plan in ZIP format called migration-plan.data

PIM planner requirements

The PIM planner requires access to the MariaDB kinton schema via the JDBC URL. 

• It encrypts the database credentials for runtime use only; it does not save or export credentials

Before you run the PIM planner

1. Start the Abiquo upgrade to 5.3 as usual including
   

   1. Stop the Abiquo platform

   2. Create backups including VM snapshots, Database dump, and Redis dump

2. Upgrade the database

3. STOP the upgrade

Run the PIM planner

To run the PIM planner do these steps.

1. Run the Abiquo upgrade to 5.3 and stop after the database upgrade

2. On the Abiquo API Server, install the Abiquo PIM tools package

   yum install abiquo-pim-tools

   By default, it should install in the /opt/abiquo/pim-tools folder

3. Run the PIM planner against your database.

   We strongly reccommend that you redirect the log in the standard output of the PIM planner to a file.

   For example:

   java -jar /opt/abiquo/pim-tools/pimplanner.jar --jdbc-url="jdbc:mysql://my.database.server:3306/kinton?autoReconnect=true&user=root&password=root" | tee output_pimplanner.log

   
   

4. Check the output file from the PIM planner
    If there are any warnings or errors, resolve them before you continue. 
   If you have any doubts, please contact Abiquo Support.

5. For ALL Remote Services servers

   1. Copy the migration-plan.data file to each Remote Services server

   Next, follow the instructions to run the PIM migrator on each Remote Services server

PIM planner options

The PIM migrator performs the provider ID migration in the compute, backup, and networking providers via the Remote Services servers.

• It updates the VMs, backups, firewalls, and load balancers in the providers and in Redis

• It also tests the migration in dry run mode

What does it output?

• An SQL file to run on the kinton database

• A log in standard output (you should redirect it to a file)

PIM migrator requirements

The PIM migrator requires the following.

• The migration plan from the PIM planner

• Access to:

  • the Redis instance of the Remote Service server.

  • the hypervisors in the datacenter

Before you run the PIM migrator

Do these steps.

1. Start the Abiquo upgrade to 5.3 as usual including
   

   1. Stop the Abiquo platform

   2. Create backups including snapshots, Database dump, and Redis dump

2. Upgrade the database

3. STOP the upgrade

4. Run the PIM planner and obtain the migration plan

Run the PIM migrator

Do these steps to run the PIM migrator.

Log in to ALL remote services servers and do these steps on EACH server. 

1. Install the PIM tools

   yum install abiquo-pim-tools

   The default install folder is /opt/abiquo/pim-tools

2. Obtain the datacenter-id of the Remote Services server from the value of the abiquo.datacenter.id property in the abiquo.properties file.

   abiquo.datacenter.id=abq_dc1

   In this case, the value of the datacenter-id parameter will be "abq_dc1"

3. Run the PIM migrator in dry run mode, which is the default mode that doesn't make any changes.

   The "-noseed" parameter is required. The default value is false, which means the migrator will use the platform's default seed file. You can specify a seed file with the "-seed" parameter. 

   We recommend that you save the log in standard output to a file. And we recommend that you give the output files names that will identify the Remote Services server.

   For example 

   java -jar /opt/abiquo/pim-tools/pimmigrator.jar -dc=abq_dc1 -redishost=localhost -plan=migration-plan.data -noseed -output=update_DC1.sql | tee pimmigrator_dry_run_DC1.log

   
   

4. Check the output file. If there are any errors or warnings, resolve them.
   If necessary, contact Abiquo Support.

5. Run the PIM migrator in update mode, by setting the "no dry run" option to true.

   java -jar /opt/abiquo/pim-tools/pimmigrator.jar -nodry -dc=abq_dc1 -redishost=localhost -plan=migration-plan.data -noseed -output=update_DC1.sql | tee pimmigrator_DC1.log

   
   

6. Copy the SQL file from the remote services server to the Abiquo database server.

   For example

   scp update_DC1.sql root@my.database.server:~/

   
   

After you run the migrator on ALL Remote Services servers, run the SQL upgrades on the database server as described in the next step. 

Update the Abiquo database server

1. Update the Abiquo database with all of the update.sql files. For example

   mysql kinton < update_DC1.sql
   mysql kinton < update_DC2.sql
   ...

   
   

Now continue with the Abiquo upgrade

PIM migrator options

PIM migrator notes

The migrator does not process the following providers.

• Hyper-V

• Networker

• Google Cloud Platform (see note below)

• Firewalls and load balancers that are not in NSX

For Google Cloud Platform, if you have VMs deployed before the upgrade, after you apply the PIM tools, do these steps:

1. Delete the VMs from the platform only 

   • in the API, delete them with the "logicaldelete" parameter set to true. See Delete a VM API doc 

2. Delete the virtual datacenters

3. Onboard the resources again

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

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

2. On the Remote services server, start the Tomcat server

   service abiquo-tomcat start

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

4. On the Monitoring server, start the Cassandra service

   sudo service cassandra start

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

6. Start the KairosDB service

   sudo service kairosdb start

7. Start the other services in this order

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

8. On the V2V server: restart the Tomcat server:

   service abiquo-tomcat restart

9. In Abiquo, re-enable the physical machines!

10. Clear your browser cache to prevent glitches in the UI