...
In the test of the upgrade to Abiquo 5.3, do these steps.
- In your lab environment, run the PIM tools as part of an upgrade test.
- 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.
- On your production system (during a quiet time), run the PIM migrator in dry-run mode (this is the default) and then resolve any warnings or errors before you continue.
...
- Start the upgrade with the usual process, and also install the PIM on all servers
- After you update the database, STOP the upgrade, and run the PIM tools as described in the following steps.
- 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.
- Check the output of the planner tool. If there are any warnings or errors, resolve them, and then run the PIM planner again.
- For ALL Remote Services servers, copy the migration plan to the server.
- On each Remote Services server, run the PIM migrator.
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. - Check the output of the PIM migrator. If there are any warnings or errors, resolve them, and then
run the PIM planner and PIM migrator again - Run the PIM migrator tool in update mode with the "--no-dry-run" option
- The PIM migrator tool will update VMs, as well as backup jobs, firewalls, and load balancers
- The PIM migrator tool will output an SQL update file. Copy this file to your database server
- While the Abiquo platform is still stopped, run the migrator's SQL update file on your database server.
The SQL update will issue warnings if you run it with Java 8 - Complete the Abiquo upgrade as usual
- After you complete the migration and restart your environment, check it as described below
- Remove the PIM tools
...