Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

...

  • 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 access to the MariaDB kinton schema via the JDBC URL. 

  • It encrypts the database credentials for runtime use only; it does not save or export credentials

When do I run the PIM planner?

Before you run the PIM planner you MUST do these steps.

  1. Start the Abiquo upgrade to 5.3 as usual including
    1. Stop the Abiquo platform
    2. Create backups including VM snapshots, Database dump, and Redis dump
  2. Upgrade the database
  3. STOP the upgrade


Run the PIM planner

To run the PIM planner do these steps.

  1. Run the Abiquo upgrade to 5.3 and stop after the database server

  2. 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

  3. Run the PIM planner against your database.

    Redirect the standard output of the PIM planner to a file (question) should they use a .txt for easier viewing (question)

    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


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

Option

Alias

Required

Description

jdbcurl

--jdbc-url

yes

Kinton JDBC URL including user and password

-output

--output-file

no

The output file. The default is 'migration-plan.data'

...