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 7 Current »

This page explains how to configure a VM to test the provider ID migration (PIM) on a dump of your production database. 

  1. Create a test VM with CentOS 7 with network connectivity.
  2. Prepare the environment. Replace XXXXX with your username and YYYYY with your password for the Abiquo repository mirror credentials:

    yum install --assumeyes http://user:passwd@mirror.abiquo.com/el7/5.3/os/x86_64/abiquo-release-ee-5.3.0-9252.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
    
    mkdir --parents /opt/abiquo/config
    touch /opt/abiquo/config/abiquo.properties
    chown tomcat:root /opt/abiquo/config/abiquo.properties
  3. Enable and start MariaDB:

    systemctl enable mariadb
    systemctl start mariadb
  4. Log in to your API server and copy the Abiquo configuration file:

    ssh myusername@myAPIserverFQDN
    scp /opt/abiquo/config/abiquo.properties root@myTestVM:/opt/abiquo/config/abiquo.properties
  5. Log in to your database server and create a database dump of the kinton database:

    mysqldump --databases kinton --routines --triggers | gzip -9 > kinton_dump_$(date +%Y%m%d_%H%M%S).sql.gz
    scp kinton_dump_*.sql.gz root@myTestVM:~/
  6. Log in to your test server and extract the database dump:

    tar -xzf kinton_dump_*.sql.gz
  7. On the test server, load the database dump

    mysql --user root --password --execute="CREATE DATABASE kinton;"
    mysql --user root --password kinton < kinton_dump_*.sql
    mysql --execute "GRANT ALL PRIVILEGES ON *.* TO 'root'@'localhost' IDENTIFIED BY '' WITH GRANT OPTION;"
  8. Update the database to version 5.3.0 :

    /usr/sbin/abiquo-db update
  9. Run the PIM planner tool:

    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
  10. Carefully review the content of the log file output_pimplanner.log: if there are any warnings or errors, please check the VMs before you continue.

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



  • No labels