Versions Compared

Old Version 13

changes.mady.by.user MS

Saved on

compared with

New Version 14

changes.mady.by.user MS

Saved on

Key

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

...

This document gives a general overview of the migration for the provider ID feature as part of the upgrade to Abiquo 5.3.0.

Tip

We expect that the provider ID migration could take a long time in large environments, so you should allow extra time for your upgrade and test it in the largest test environment that you have available.

Abiquo has developed a set of provider ID migration (PIM) tools to run once to upgrade the platform and adapt the platform data to the new identifier. The tools are jar files in a separate RPM package.

We expect that the provider ID migration could take a long time in large environments, so allow extra time for your upgrade, and test it in the largest test environment that you have available.

Warning

You must test this update in a lab environment before you run it in your production environment.

Before you upgrade to Abiquo 5.3 you must:

  1. Create a full backup of the platform
  2. Create dumps of the database and Redis.

PIM processes

...

Upgrade test process

In the test of the upgrade to Abiquo 5.3, do these steps

  1. In your lab environment, run the PIM tools as part of an upgrade test.
  2. On a test VM, add a dump of your production database, run liquibase to update the database to 5.3, and run the PIM planner. See Create a test VM and run PIM planner on a database dump .
  3. On your production system (during a quiet time), run the PIM migrator in dry-run mode (this is the default mode)) and then resolve any warnings or errors before you continue.

Upgrade process

In the upgrade to Abiquo 5.3 do these steps.

  1. Create a full backup of your platform, and dumps of your database and Redis systems.
  2. On your production system, perform start the Abiquo upgrade, and after you update the database, stop STOP the upgrade, run the PIM tools, and then continue the upgrade

...

  1. Perform the upgrade with the usual process, and after you update the database, run the PIM tools as described here.
  2. Run the PIM planner tool against your database. This tool will create a migration plan for all of your VMs and list the required migration steps. 
  3. Check the output of the planner tool. If there are any warnings or errors, resolve them and then run the PIM planner again.
  4. For ALL Remote Services servers, copy the migration plan to the server.
  5. On each Remote Services server, run the migration plan. 
    (tick) By default the PIM migrator tool will run in "dry run" mode. For each entity in the migration plan, the PIM migrator tool will connect to the provider and compute the provider ID.
  6. Check the output of the PIM migrator tool. If there are any warnings or errors, resolve them and then run the PIM planner and PIM migrator again (question)
  7. Run the PIM migrator tool in update mode with the "--no-dry-run" option.
    1. The PIM migrator tool will update VMs, as well as backup jobs, firewalls, load balancers, (question).
    2. The PIM migrator tool will output an SQL update file.
  8. While the Abiquo platform is still stopped, run the migrator's SQL update file.
    (info) The SQL update will issue warnings if you run it with Java 8
  9. After you complete the migration and restart your environment, check it as described below

PIM tools database test environment

To run the PIM tools on the dump of your production database, you will need:

  • Docker or VM with MySQL
  • A dump of your production database
  • Abiquo RPMs
    • Abiquo PIM tools package
    • Abiquo model package

...

Check your environment

The migration should only change the identification of deployed VMs in Abiquo. After you migrate to provider ID, you can perform the following checks: 

...