Page Comparison

...

• An SQL file to run on the kinton database
• A log in standard output (you should redirect it to a file)

...

PIM migrator requirements

The PIM migrator requires the following.

• The migration plan from the PIM planner
• Access to:  does this mean network access, anything else like root user 
  • the Redis instance of the Remote Service server.
  • the hypervisors in the datacenter

...

Before you run the PIM migrator

...

1. Start the Abiquo upgrade to 5.3 as usual including
   
   1. Stop the Abiquo platform
   2. Create backups including snapshots, Database dump, and Redis dump
2. Upgrade the database
3. STOP the upgrade
4. Run the PIM planner and obtain the migration plan

Run the PIM migrator

Log in to ALL Remote Services Servers and do these steps on EACH server. 

1. Install the PIM tools

   Code Block
   yum install abiquo-pim-tools

   The default install folder is /opt/abiquo/pim-tools

2. Obtain the datacenter-id of the Remote Services server from the value of the abiquo.datacenter.id property in the abiquo.properties file.

   Code Block
   abiquo.datacenter.id=abq_dc1

   In this case, the value of the datacenter-id parameter will be "abq_dc1"

3. Run the PIM migrator.

   We recommend that you save the log in standard output to a file. And we recommend that you give the output files names that will identify the Remote Services server.

   For example:

   Code Block
   java -jar /opt/abiquo/pim-tools/pimmigrator.jar -dc=abq_dc1 -redishost=localhost -plan=migration-plan.data -noseed -output=update_DC1.sql > pimmigrator_DC1.log

   
   

4. Check the output file. If there are any errors or warnings, resolve them.
   If necessary, contact Abiquo Support.

5. Copy the SQL file from the Remote Services server to the Abiquo database server.

   For example

   Code Block
   scp update_DC1.sql root@my.database.server:~/

   
   

...