Abiquo Documentation Cookies Policy

Our Documentation website uses cookies to improve your experience. Please visit our Cookie Policy page for more information about cookies and how we use them.

Abiquo 4.7

Skip to end of metadata
Go to start of metadata

Admin Guide 1. Abiquo: Upgrading

This section describes how to prepare to upgrade from any previous version of Abiquo 3.x 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

    On standard environment, the RabbitMQ service is in 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. Abiquo Server

    service abiquo-tomcat stop
    service httpd stop
  2. Remote Services

    service abiquo-tomcat stop
  3. V2V Server
    1. The BPM remote service is run on-demand only, so there is no need to stop anything

  4. KVM

    service abiquo-aim stop
  5. LVM

    service abiquo-lvmiscsi stop

4. Back up the main platform elements

  1. Back up the Abiquo MySQL DBs:

    mysqldump --routines --triggers kinton            > kinton.sql-$(date +%s)
    mysqldump --routines --triggers kinton_accounting > kinton_accounting.sql-$(date +%s)
  2. Dump the redis datastore and back it up:

    redis-cli save
    cp -a /var/lib/redis /var/lib/redis-$(date +%s)
  3. Back up /opt/abiquo folder in all Abiquo platform servers:

    tar cvfz /opt/abiquo.tgz-$(date +%s) /opt/abiquo
  4. Backup the UI:

    tar cvfz /var/www/html/ui.tgz-$(date +%s) /var/www/html/ui