Page Comparison

...

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. 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. 
    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 
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, .
   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.
    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 the same MySQL version
• Dump of your production database
• Abiquo database from a pre-5.3 system
• 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: 

...