Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

...

...

From version

To version

Upgrade type

Notes

5.4.x

6.0.x

Standard

Follow the process in this document (or the upgrade at Upgrade Abiquo 5.4 to 6.0.x distributed by servers document )

6.0.x

6.1.x

Standard

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

...


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

...

  • .

SAML 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

...

  • .

Note

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

Note

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



Table of contents

Table of Contents

...

  1. In the UI in the Infrastructure view, select each physical machine and click Disable

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


...


Check for operations in progress on the platform

Before you shut down the platform servers you should , check that no operations are in progress.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.

    Code Block
    # rabbitmqctl list_queues messages name

    Code Block
    # 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

    Code Block
    $ ps aux | grep v2v
    $ ps aux | grep mechadora

...

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

      Code Block
      yum remove 'abiquo-release-*'
    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:

      Code Block
      yum localinstall http://user:passwd@mirror.abiquo.com/el7/6.1/os/x86_64/abiquo-release-ee-6.1.0-20230112_211400.el7.noarch.rpm

      For Abiquo 6.1.1, the release package would be:

      Code Block
      http://use:passwd@mirror.abiquo.com/el7/6.1/updates/x86_64/abiquo-release-ee-6.1.1-20230511_170351.el7.noarch.rpm

    4. For major versions, disable the updates repo. See https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/deployment_guide/sec-managing_yum_repositories

...