This page explains how to configure a VM to test the provider ID migration (PIM) on a dump of your production database.
Author: Former user (Deleted)
- Obtain Create a test VM with CentOS 7 with network connectivity.
Install Abiquo release package, disable updates, install the required packagesPrepare the environment. Replace XXXXX with your username and YYYYY with your password for the Abiquo repository mirror credentials:
Code Block yum install --assumeyes http://user:passwd@mirror.abiquo.com/el7/5.3/os/x86_64/abiquo-release-ee-5.3.0-92439252.el7.noarch.rpm yum-config-manager --disable abiquo-updates yum-config-manager --save --setopt=abiquo-*.username=XXXXX yum-config-manager --save --setopt=abiquo-*.password=YYYYY yum install --assumeyes abiquo-model abiquo-pim-tools abiquo-core mariadb-server liquibase
Make a config folder and from your API server, copy the abiquo.properties file
Code Block mkdir -p-parents /opt/abiquo/config scp root@my.api.server:touch /opt/abiquo/config/abiquo.properties chown tomcat:root /opt/abiquo/config/abiquo.properties
Enable and start MariaDB:
Code Block systemctl enable mariadb systemctl start mariadb
Log in to your API server and copy the Abiquo configuration file:
Code Block ssh myusername@myAPIserverFQDN scp /opt/abiquo/config/abiquo.properties root@myTestVM:/opt/abiquo/config/abiquo.properties
Log in to your database server and create a database dump of the main database and the accounting database kinton database:
Code Block mysqldump --databases kinton kinton_accounting --routines --triggers | gzip -9 > kinton_kinton_accounting_dump_$(date +%Y%m%d_%H%M%S).sql.gz scp kinton_kinton_accounting_dump_20210831_205241*.sql.gz root@my.test.serverroot@myTestVM:~/
Log in to your test server and uncompress extract the database dump:
Code Block tar -xzf kinton_kinton_accounting_dump_20210831_205241*.sql.gz
On the test server, load the database dump
Code Block mysql --user root -e -password --execute="CREATE DATABASE kinton;" mysql --user root --password kinton < kinton_kinton_accounting_dump_20210831_205241*.sql mysql -e-execute "GRANT ALL PRIVILEGES ON *.* TO 'root'@'localhost' IDENTIFIED BY '' WITH GRANT OPTION;"
Update the database to version 5.3.0 :
Code Block /usr/sbin/abiquo-db update
Run the PIM planner tool:
Code Block java -jar /opt/abiquo/pim-tools/pimplanner.jar --jdbc-url="jdbc:mysql://127.0.0.1:3306/kinton?autoReconnect=true&user=root&password=" > output_pimplanner.log
Check the Carefully review the content of the log file output_pimplanner.log file. If : if there are any warnings or errors, please check the VMs before you continue.
- We kindly encourage you to dry run the pimmigrator tool as detailed in the Upgrade Abiquo documentation, so you can check in advance that the migration plan works as expected in each one of your real RS servers.