Abiquo 5.3 introduces the provider ID as a unique VM identifier for deployed VMs. The Abiquo UUID will continue as the VM's identifier in the API, even when undeploying and deploying the VM again.
This document gives a general overview of the migration for the provider ID feature as part of the upgrade to Abiquo 5.3.0.
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 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.
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:
- Create a full backup of the platform
- Create dumps of the database and Redis.
Overview
- Run the PIM tools in your lab environment
- Create a test system, add a dump of your production database, run liquibase to update the database to 5.3, and run the PIM planner
- Run the PIM migrator in dry-run mode on your production system
- 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.
- Perform the upgrade with the usual process, and after you update the database, run the PIM tools as described here.
- 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 migration plan. 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 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. - 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
- 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, load balancers, .
- The PIM migrator tool will output an SQL update file.
- The PIM migrator tool will update VMs, as well as backup jobs, firewalls, load balancers,
- 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 - 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:
- List the Redis subscriptions, which will use the Provider ID as the unique key
- Use the VSM console to check the other entities
- If you are using Veeam, log in to the backup server and check the names of the backup jobs, which will now include the ProviderID
After you start Abiquo, log in as the cloud administrator and check VMs, firewalls, load balancers, and so on.