Versions Compared

Old Version 36

changes.mady.by.user MS

Saved on

compared with

New Version 37

changes.mady.by.user MS

Saved on

Key

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


Excerpt
hiddentrue

Upgrade or update your Abiquo hybrid cloud platform.

Image Removed

This section describes how to upgrade from Abiquo 4.7.0 or above to 5.2.x. Please contact Abiquo Support for further information.

Table of Contents
maxLevel2

Numberedheadings
start-numbering-ath2
Warning
titleMajor upgrade

The upgrade to Abiquo 5.2.0 is a major upgrade with upgrades of third-party software packages that are critical platform dependencies

You must make snapshots of ALL servers before you start the upgrade


Note
  • Abiquo YUM repositories are no longer open, please contact Abiquo Support to obtain your credentials
  • This upgrade process starts from Abiquo 4.7 or above. To upgrade from earlier versions, please contact Abiquo Support


Prepare branding

  • If you are upgrading from Abiquo 4.7.x, the new UI in Abiquo 5.0 requires new branding. See Abiquo branding guide


...


Prevent cloud users from performing VM operations

  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.

Check for operations in progress on the platform

Include Page
Check for operations in progress on the platform
Check for operations in progress on the platform


...

Disable old billing dashboards and delete last bills

In Abiquo 5.2, the billing dashboard feature is now in the core Abiquo platform.

If you are using the billing dashboard scripts from previous versions, disable them and delete last bills before you continue with the upgrade.

  1. On the server where you were running the billing packages, remove the Cron jobs to run the billing scripts.

    Code Block
    # rm /etc/cron.d/abiquo-billing-ec2
# rm /etc/cron.d/abiquo-billing-arm


  2. Delete the last bills from the previous version of the billing dashboards (from the kinton.billing_consolidation and kinton.billing_register tables), see commands below. Remove the bills for Azure and Amazon providers, for the number of months covered by the abiquo.enterprise.property.billing.monthoffset system property, which has a default value of 2 months. Later the new billing dashboards feature will regenerate these bills:

    Code Block
    SELECT COUNT(*) FROM kinton.billing_consolidation;
SELECT COUNT(*) FROM kinton.billing_register;


...

Back up the main platform elements

Back up the main platform elements

Include Page
Back up the main platform elements
Back up the main platform elements


Note

If you are using HTTPS-SSL between your Tomcat servers, for each Tomcat server:

From the /opt/abiquo/tomcat/conf folder, back up the server.xml files. You will need to restore and modify them after the yum upgrade.

See Upgrade Tomcat 8 to Tomcat 9 with HTTPS TLS.


...

Stop platform services

Stop platform services

Include Page
Stop platform services
Stop platform services


...


Make snapshots and backups of all platform servers

The upgrade to Abiquo 5.2.x is a major upgrade with upgrades of third-party software packages that are critical platform dependencies

You MUST make snapshots of all servers in your platform before you upgrade to Abiquo 5.2.x.


...

Prepare yum repositories on all servers

Prepare yum repositories on all servers for v5.2

Include Page
Prepare yum repositories on all servers for v5.2
Prepare yum repositories on all servers for v5.2


...

Upgrade monolithic server

Upgrade Abiquo Monolithic to v5.2.x

Include Page
Upgrade Monolithic Server to v5.2
Upgrade Monolithic Server to v5.2


...


Upgrade monitoring server

Upgrade monitoring server to v5.2

Include Page
Upgrade monitoring server to v5.2
Upgrade monitoring server to v5.2


...

Upgrade steps from 4.7.x to 5.0.x

Start with your original version and perform the steps to the final version.

Expand
titleClick for Upgrade steps from 4.7.x to 5.0.x


Upgrade steps from

5

4.

0

7.x to 5.

1

0.x

Start with your original version and perform the steps to the final version.

Click for

Include Page
Upgrade steps from

5

4.

0

7.x to 5.

1

0.x

for Veeam

Click for Mandatory

Upgrade steps from

5

4.

0

7.x to 5.

1.2 or 5.2.x for VM names

0.x



...


Upgrade steps from 5.

...

0.x to 5.

...

1.x

Start with your original version and perform the steps to the final version.

...

1. or 51.1 2 or above, follow the steps from the
Expand
titleClick for Upgrade steps from 5.
0
.
x to 5.1.
x for Veeam

Upgrade steps from 5.0.x to 5.1.x block.

Click for

for Veeam

Include Page
Upgrade steps from 5.

1

0.x to 5.

2

1.x for

Azure

Veeam

Click for

Upgrade steps from 5.

1

0.x to 5.

2

1.x for

Tomcat (step 3 is mandatory)

Veeam


1 Redis
Expand
titleClick for Upgrade steps from 5.
0.x to 5.1.2 or 5.2.x for
VM names
Click for

Upgrade steps from 5.

1

0.x to 5.1.2 or 5.2.x for

billing dashboards

VM names

Include Page
Upgrade

steps for 5.2 versions
Numberedheadings
start-numbering-ath2
Major upgrade

The upgrade to Abiquo 5.2.0 is a major upgrade with upgrades of third-party software packages that are critical platform dependencies

You must make snapshots of ALL servers before you start the upgrade

  • Abiquo YUM repositories are no longer open, please contact Abiquo Support to obtain your credentials
  • This upgrade process starts from Abiquo 4.7 or above. To upgrade from earlier versions, please contact Abiquo Support

Prepare branding

If you are upgrading from Abiquo 4.7.x, the new UI in Abiquo 5.0 requires new branding. See

Prevent cloud users from performing VM operations

  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.

Disable old billing dashboards and delete last bills

In Abiquo 5.2, the billing dashboard feature is now in the core Abiquo platform.

If you are using the billing dashboard scripts from previous versions, disable them and delete last bills before you continue with the upgrade.

On the server where you were running the billing packages, remove the Cron jobs to run the billing scripts.

Delete the last bills from the previous version of the billing dashboards (from the kinton.billing_consolidation and kinton.billing_register tables), see commands below. Remove the bills for Azure and Amazon providers, for the number of months covered by the abiquo.enterprise.property.billing.monthoffset system property, which has a default value of 2 months. Later the new billing dashboards feature will regenerate these bills:

Back up the main platform elements

If you are using HTTPS-SSL between your Tomcat servers, for each Tomcat server:

From the /opt/abiquo/tomcat/conf folder, back up the server.xml files. You will need to restore and modify them after the yum upgrade.

See .

Stop platform services

Make snapshots and backups of all platform servers

The upgrade to Abiquo 5.2.x is a major upgrade with upgrades of third-party software packages that are critical platform dependencies

You MUST make snapshots of all servers in your platform before you upgrade to Abiquo 5.2.x.

Prepare yum repositories on all servers

Upgrade monolithic server

Upgrade monitoring server

Upgrade steps from 4.7.x to 5.0.x

Start with your original version and perform the steps to the final version.

Click for Upgrade steps from 4.7.x to 5.0.x

Upgrade steps from 5.0.x to 5.1.x

Start with your original version and perform the steps to the final version.

Click for Upgrade steps from 5.0.x to 5.1.x for VeeamClick for Mandatory Upgrade steps from 5.0.x to 5.1.2 or 5.2.x for VM names

These

steps
apply to upgrades starting
from
version
5.
2.
0
and above.

Click here to show/hide the steps to upgrade 5.2 versions

Configure Abiquo after the upgrade

Before you start the Abiquo tomcat server, add  to the abiquo.properties file.
By default the abiquo.properties file is found in the /opt/abiquo/config/ folder.
See 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
If your API is not in the same domain as the UI, set the API endpoint pointing to your Abiquo API server:
  • Reporting changes: To upgrade the Abiquo Reports database for the upgrade to Abiquo 4.7.x+, contact Abiquo Support for the file and procedure.

    • Start Abiquo servers and services

    Excerpt
    hiddentrue

    Upgrade or update your Abiquo hybrid cloud platform.

    Image Removed

    This section describes how to upgrade from Abiquo 4.7.0 or above to 5.2.x. Please contact Abiquo Support for further information.

    Table of Contents
    maxLevel2

    .x to 5.1.2 or 5.2.x for VM names
    Upgrade steps from 5.0.x to 5.1.2 or 5.2.x for VM names



    ...


    Upgrade steps from 5.1.x to 5.2.x

    Start with your original version and perform the steps to the final version.

    When upgrading from 5.1.0 or 5.1.1 to 5.1.2 or above, follow the steps from the Upgrade steps from 5.0.x to 5.1.x block.


    Expand
    titleClick for Upgrade steps from 5.1.x to 5.2.x for Azure

    Upgrade steps from 5.1.x to 5.2.x for Azure

    Include Page
    Upgrade steps from 5.1.x to 5.2.x for Azure
    Upgrade steps from 5.1.x to 5.2.x for Azure




    Expand
    titleClick for Upgrade steps from 5.1.x to 5.2.x for Tomcat (step 3 is mandatory)

    Upgrade steps from 5.1.x to 5.2.x

    Start with your original version and perform the steps to the final version.

    When upgrading from 5.1.0 or 5.1.1 to 5.1.2 or above, follow the steps from the for Tomcat with TLS

    Include Page
    Upgrade steps from 5.
    0
    1.x to 5.
    1
    2.x
    block.

    Click for

    for Tomcat with TLS
    Upgrade steps from 5.1.x to 5.2.x for

    AzureClick for

    Tomcat with TLS


    Expand
    titleClick for Upgrade steps to remove old VSM definitions for Redis

    Upgrade steps to remove old VSM definitions for Redis

    Include Page
    Upgrade steps to remove old VSM definitions for Redis
    Upgrade steps to remove old VSM definitions for Redis





    Expand

    Upgrade steps from 5.1.x to 5.2.x for

    Tomcat (step 3 is mandatory)Click for

    billing dashboards

    Include Page
    Upgrade steps from 5.1.x to 5.2.x for

    Redis

    billing dashboards

    Click for

    Upgrade steps from 5.1.x to 5.2.x for billing dashboards





    Upgrade steps for 5.2 versions

    These steps apply to upgrades starting from version 5.2.0 and above.

    Click here to show/hide the steps to upgrade
    Expand
    titleClick for Upgrade steps for 5.2 versions

    Upgrade steps for 5.2 versions

    Upgrade steps for 5.2 versions

    Include Page
    Upgrade steps for 5.2 versions
    Upgrade steps for 5.2 versions





    ...


    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:

      Code Block
      {
    "config.endpoint": "http://myAPIserver/api"
}


    3. Reporting changes: To upgrade the Abiquo Reports database for the upgrade to Abiquo 4.7.x+, contact Abiquo Support for the file and procedure.


    ...


    Start Abiquo servers and services

    Start Abiquo servers and services

    Include Page
    Start Abiquo servers and services
    Start Abiquo servers and services