Versions Compared

Old Version 4

changes.mady.by.user MS

Saved on

compared with

New Version 5

changes.mady.by.user MS

Saved on

Key

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

...

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.

...


Overview

  1. Run the PIM tools in your lab environment
  2. Create a test system, add a dump of your production database, run liquibase to update the database to 5.3, and run the PIM

...

Info

To keep your database credentials secure, the PIM tools use runtime encryption. 

Full PIM migration process in a lab environment

First run the full PIM migration process in your lab environment.

Start the upgrade process

Run the upgrade process as usual and stop after you update the database.

...

  1. planner
  2. Run the PIM migrator in dry-run mode on your production system
  3. Perform the upgrade, and after you update the database, run the PIM tools


PIM tools process description

To run the PIM tools do the following steps.

  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 migration plan and resolve any warnings or errors.

...

  1. Then run the PIM planner again
  2. For ALL Remote Services servers, copy the migration plan to the server. 
  3. On each Remote Services server, run the migration plan. By  
    (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.
  4. Check the output of the PIM migrator tool and resolve any warnings or errors.

Stage 3: migration

  1. Run the PIM planner and PIM migrator again.
  2. 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.
    2. The PIM migrator tool will output an SQL update file.
  3. While the Abiquo platform is still stopped, run the migrator's SQL update file.
    The (info) The SQL update will issue may issue warnings if you run it with Java 8. 
  4. After you complete the migration and restart your environment, check it as described below


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: 

...