Page Comparison

...

• The PIM planner connects to the Abiquo kinton database and extracts the data for the PIM migrator tool.
  It doesn

  • The PIM planner will process each deployed VM to:

    1. Compute the provider ID
    2. Define the rename of any backup jobs or groups
    3. Define the rename of any firewalls and load balancers
  • The PIM planner doesn't make any changes to the platform

  ...

  • A log in standard output (you should redirect it to a file)
  • A migration plan in ZIP format called migration-plan.data

  Requirements

  The PIM planner requires:

  ...

  requires access to the MariaDB kinton schema via the JDBC URL. 

  • • It encrypts the
  DB
  • • database credentials
  at
  • • for runtime
  and
  • • use only; it does not save or export
  them to 
  • • credentials

  Run the PIM planner

  To run the PIM planner do these steps:.

  Warning
  Before you run the PIM planner you MUST: Start the Abiquo upgrade to 5.3 as usual including Stop the Abiquo platform Create backups including snapshots, Database dump, and Redis dump Upgrade the database STOP the upgrade

  ...

  1. On the Abiquo API Server, install the Abiquo PIM tools package

     Code Block
     yum install abiquo-pim-tools

     By default, it should install in the /opt/abiquo/pim-tools folder

  2. Run the PIM planner against your database. Redirect the standard output of the PIM planner to a file  should they use a .txt for easier viewing 

     For example:

     Code Block
     java -jar /opt/abiquo/pim-tools/pimplanner.jar --jdbc-url="jdbc:mysql://my.database.server:3306/kinton?autoReconnect=true&user=root&password=root" > output_pimplanner.log

     The PIM planner will process each VM to:

  3. Compute the provider ID
  4. Define the rename of any backup jobs or groups
  Define the rename of any firewalls and load balancers

  
  

  5. Check the output file from the PIM planner
      If there are any warnings or errors, resolve them before you continue. If you have any doubts, please contact Abiquo Support.
  6. For ALL Remote Services servers 
     1. Copy the migration-plan.data file to each Remote Services server
     2. Follow the instructions to run the PIM migrator on each Remote Services server
        
        

  ...