Prepare to upgrade Abiquo

This section describes how to prepare to upgrade from any previous version of Abiquo to the current version. Please contact Abiquo Support for further information.

1. Prevent cloud users from performing VM operations

• In the UI Infrastructure tab, select each physical machine and click Disable

• Using the API, set the state of each physical machine to DISABLED

2. Check for operations in progress on the platform

1. Check that the Abiquo RabbitMQ queues are empty. The number of messages in all queues must be 0:
   
   

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

    

    In a standard environment, the RabbitMQ service is on the Abiquo API server. Depending on the environment, this will be the Abiquo Monolithic or the Abiquo Server appliance.

    

2. Check for any active V2V conversions by checking for the V2V or Mechadora processes

   $ ps aux | grep v2v $ ps aux | grep mechadora

    

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

    

3. Stop remote services server

    

4. Stop the database on the monolithic server or database server.

   For a datanode configuration, you will also need to stop the Galera cluster. For more details, see Stop and start HA configuration
   
   

5. Stop RabbitMQ (on the monolithic server or API server or Datanode)

    

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

7. Stop monitoring server

    

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

    

4. Back up the main platform elements