Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Introduction to the PIM planner

What does it do?

  • The PIM planner connects to the Abiquo kinton database and extracts the data for the PIM migrator tool.
    • 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

What is the output?

  • 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

Run the PIM planner

To run the PIM planner do these steps.

Before you run the PIM planner you MUST:

  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
  1. On the Abiquo API Server, install the Abiquo PIM tools package

    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 (question) should they use a .txt for easier viewing (question)

    For example:

    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
  3. 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.
  4. 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

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'

  • No labels