1.4. Migrating Data Warehouse and Reports to Separate Machines

Procedure 1.9. Migrating the Data Warehouse Database to a Separate Machine

1. On the existing database machine, dump the ovirt_engine_history database into a SQL script file:

   # pg_dump ovirt_engine_history > ovirt_engine_history.sql

   Copy to Clipboard Toggle word wrap
2. Copy the script file from the existing database machine to the new database machine.
3. Restore the ovirt_engine_history database on the new database machine:

   # psql -d ovirt_engine_history -f ovirt_engine_history.sql

   Copy to Clipboard Toggle word wrap
   The command above assumes that the database on the new machine is also named ovirt_engine_history.

Procedure 1.10. Step 1: Setting up the New Data Warehouse Machine

1. Register your system with the Content Delivery Network, entering your Customer Portal user name and password when prompted:

   # subscription-manager register

   Copy to Clipboard Toggle word wrap
2. Find the Red Hat Enterprise Linux Server and Red Hat Enterprise Virtualization subscription pools and note down the pool IDs.

   # subscription-manager list --available

   Copy to Clipboard Toggle word wrap
3. Use the pool IDs located in the previous step to attach the entitlements to the system:

   # subscription-manager attach --pool=pool_id

   Copy to Clipboard Toggle word wrap
4. Disable all existing repositories:

   # subscription-manager repos --disable=*

   Copy to Clipboard Toggle word wrap
5. Enable the required channels:

   # subscription-manager repos --enable=rhel-6-server-rpms
   # subscription-manager repos --enable=rhel-6-server-supplementary-rpms
   # subscription-manager repos --enable=rhel-6-server-rhevm-3.6-rpms
   # subscription-manager repos --enable=jb-eap-6-for-rhel-6-server-rpms

   Copy to Clipboard Toggle word wrap
6. Ensure that all packages currently installed are up to date:

   # yum update

   Copy to Clipboard Toggle word wrap
7. Install the rhevm-dwh-setup package:

   # yum install rhevm-dwh-setup

   Copy to Clipboard Toggle word wrap

Procedure 1.11. Step 2: Stopping the Data Warehouse Service on the Manager Machine

1. Stop the Data Warehouse service:

   # service ovirt-engine-dwhd stop

   Copy to Clipboard Toggle word wrap
2. If the ovirt_engine_history database, the Manager database, or both are hosted on the Manager machine and were configured by a previous version (Red Hat Enterprise Virtualization 3.4 or prior) that was then upgraded, you must allow the new Data Warehouse machine to access them. Edit the /var/lib/pgsql/data/postgresql.conf file and modify the listen_addresses line so that it matches the following:

   listen_addresses = '*'

   Copy to Clipboard Toggle word wrap
   If the line does not exist or has been commented out, add it manually.
   If one or both databases are hosted on a remote machine, you must manually grant access by editing the postgres.conf file on each machine, and adding the listen_addresses line, as above. If both databases are hosted on the Manager machine and were configured during a clean setup of Red Hat Enterprise Virtualization Manager 3.5, access is granted by default.
3. Restart the postgresql service:

   # service postgresql restart

   Copy to Clipboard Toggle word wrap

Procedure 1.12. Step 3: Configuring the New Data Warehouse Machine

1. Run the engine-setup command to begin configuration of Data Warehouse on the machine:

   # engine-setup

   Copy to Clipboard Toggle word wrap
2. Press Enter to configure Data Warehouse:

   Configure Data Warehouse on this host (Yes, No) [Yes]:
   

   Copy to Clipboard Toggle word wrap
3. Press Enter to automatically configure the firewall, or type No and press Enter to maintain existing settings:

   Setup can automatically configure the firewall on this system.
   Note: automatic configuration of the firewall may overwrite current settings.
   Do you want Setup to configure the firewall? (Yes, No) [Yes]:

   Copy to Clipboard Toggle word wrap
   If you choose to automatically configure the firewall, and no firewall managers are active, you are prompted to select your chosen firewall manager from a list of supported options. Type the name of the firewall manager and press Enter. This applies even in cases where only one option is listed.
4. Press Enter to accept the automatically detected hostname, or enter an alternative hostname and press Enter:

   Host fully qualified DNS name of this server [autodetected host name]:

   Copy to Clipboard Toggle word wrap
5. Answer the following question about the location of the ovirt_engine_history database:

   Where is the DWH database located? (Local, Remote) [Local]: Remote
   

   Copy to Clipboard Toggle word wrap
   Type the alternative option as shown above and then press Enter.
6. Enter the fully qualified domain name and password for your ovirt_engine_history database host. Press Enter to accept the default values in each other field:

   DWH database host []: dwh-db-fqdn
   DWH database port [5432]: 
   DWH database secured connection (Yes, No) [No]: 
   DWH database name [ovirt_engine_history]: 
   DWH database user [ovirt_engine_history]: 
   DWH database password: password

   Copy to Clipboard Toggle word wrap
7. Enter the fully qualified domain name and password for the Manager database machine. Press Enter to accept the default values in each other field:

   Engine database host []: engine-db-fqdn
   Engine database port [5432]: 
   Engine database secured connection (Yes, No) [No]: 
   Engine database name [engine]: 
   Engine database user [engine]: 
   Engine database password: password

   Copy to Clipboard Toggle word wrap
8. Press Enter to create a backup of the existing Data Warehouse database:

   Would you like to backup the existing database before upgrading it? (Yes, No) [Yes]:

   Copy to Clipboard Toggle word wrap
   The time and space required for the database backup depends on the size of the database. It may take several hours to complete. If you choose not to back up the database here, and engine-setup fails for any reason, you will not be able to restore the database or any of the data within it. The location of the backup file appears at the end of the setup script.
9. Confirm that you want to permanently disconnect the existing Data Warehouse service from the Manager:

   Do you want to permanently disconnect this DWH from the engine? (Yes, No) [No]:

   Copy to Clipboard Toggle word wrap
10. Confirm your installation settings:

    Please confirm installation settings (OK, Cancel) [OK]:
    

    Copy to Clipboard Toggle word wrap

Procedure 1.13. Step 4: Removing the Data Warehouse Package from the Manager Machine

1. Remove the Data Warehouse package:

   # yum remove rhevm-dwh

   Copy to Clipboard Toggle word wrap
   This step prevents the Data Warehouse service from attempting to automatically restart after an hour.
2. Remove the Data Warehouse files:

   # rm -rf /etc/ovirt-engine-dwh /var/lib/ovirt-engine-dwh

   Copy to Clipboard Toggle word wrap

Procedure 1.14. Step 1: Configuring the New Reports Machine

1. Register your system with the Content Delivery Network, entering your Customer Portal user name and password when prompted:

   # subscription-manager register

   Copy to Clipboard Toggle word wrap
2. Find the Red Hat Enterprise Linux Server and Red Hat Enterprise Virtualization subscription pools and note down the pool IDs.

   # subscription-manager list --available

   Copy to Clipboard Toggle word wrap
3. Use the pool IDs located in the previous step to attach the entitlements to the system:

   # subscription-manager attach --pool=pool_id

   Copy to Clipboard Toggle word wrap
4. Disable all existing repositories:

   # subscription-manager repos --disable=*

   Copy to Clipboard Toggle word wrap
5. Enable the required channels:

   # subscription-manager repos --enable=rhel-6-server-rpms
   # subscription-manager repos --enable=rhel-6-server-supplementary-rpms
   # subscription-manager repos --enable=rhel-6-server-rhevm-3.6-rpms
   # subscription-manager repos --enable=jb-eap-6-for-rhel-6-server-rpms

   Copy to Clipboard Toggle word wrap
6. Ensure that all packages currently installed are up to date:

   # yum update

   Copy to Clipboard Toggle word wrap
7. Install the rhevm-reports-setup package:

   # yum install rhevm-reports-setup

   Copy to Clipboard Toggle word wrap
8. Run the engine-setup command to begin configuration of Reports on the machine:

   # engine-setup

   Copy to Clipboard Toggle word wrap
9. Press Enter to configure Reports:

   Configure Reports on this host (Yes, No) [Yes]:
   

   Copy to Clipboard Toggle word wrap
10. Press Enter to automatically configure the firewall, or type No and press Enter to maintain existing settings:

    Setup can automatically configure the firewall on this system.
    Note: automatic configuration of the firewall may overwrite current settings.
    Do you want Setup to configure the firewall? (Yes, No) [Yes]:

    Copy to Clipboard Toggle word wrap
    If you choose to automatically configure the firewall, and no firewall managers are active, you are prompted to select your chosen firewall manager from a list of supported options. Type the name of the firewall manager and press Enter. This applies even in cases where only one option is listed.
11. Press Enter to accept the automatically detected hostname, or enter an alternative hostname and press Enter:

    Host fully qualified DNS name of this server [autodetected host name]:

    Copy to Clipboard Toggle word wrap
12. Enter the fully qualified domain name of the Manager machine, and then press Enter:

    Host fully qualified DNS name of the engine server []:

    Copy to Clipboard Toggle word wrap
13. Answer the following questions about the ovirt_engine_reports database. Press Enter to allow setup to create and configure a local database:

    Where is the Reports database located? (Local, Remote) [Local]:
    Setup can configure the local postgresql server automatically for the Reports to run. This may conflict with existing applications.
    Would you like Setup to automatically configure postgresql and create Reports database, or prefer to perform that manually? (Automatic, Manual) [Automatic]:
    

    Copy to Clipboard Toggle word wrap
14. Enter the fully qualified domain name and password for your ovirt_engine_history database host. Press Enter to accept the default values in each other field:

    DWH database host []: dwh-db-fqdn
    DWH database port [5432]: 
    DWH database secured connection (Yes, No) [No]: 
    DWH database name [ovirt_engine_history]: 
    DWH database user [ovirt_engine_history]: 
    DWH database password: password

    Copy to Clipboard Toggle word wrap
15. Press Enter to allow setup to sign the Reports certificate and Apache certificate on the Manager via SSH:

    Setup will need to do some actions on the remote engine server. Either automatically, using ssh as root to access it, or you will be prompted to manually perform each such action.
    Please choose one of the following:
    1 - Access remote engine server using ssh as root
    2 - Perform each action manually, use files to copy content around
    (1, 2) [1]:

    Copy to Clipboard Toggle word wrap
16. Press Enter to accept the default SSH port, or enter an alternative port number and then press Enter:

    ssh port on remote engine server [22]:

    Copy to Clipboard Toggle word wrap
17. Enter the root password for the Manager machine:

    root password on remote engine server manager-fqdn.com:

    Copy to Clipboard Toggle word wrap
18. Press Enter to allow automatic configuration of SSL on Apache:

    Setup can configure apache to use SSL using a certificate issued from the internal CA.
    Do you wish Setup to configure that, or prefer to perform that manually? (Automatic, Manual) [Automatic]:
    

    Copy to Clipboard Toggle word wrap
19. Set a password for the Reports administrative users (admin and superuser). Note that the reports system maintains its own set of credentials that are separate to those used for the Manager:

    Reports power users password:

    Copy to Clipboard Toggle word wrap
    You are prompted to enter the password a second time to confirm it.
20. Confirm your installation settings:

    Please confirm installation settings (OK, Cancel) [OK]:

    Copy to Clipboard Toggle word wrap

Procedure 1.15. Step 2: Migrating Saved Reports to the New Reports Machine

1. On the Manager machine, run the ovirt-engine-reports-tool command:

   # ovirt-engine-reports-tool
   

   Copy to Clipboard Toggle word wrap
2. Enter the number that corresponds to the export option, and press Enter:

   (2) Export Jasperreports saved reports to a zip file
   (1, 2, 3) []: 2
   

   Copy to Clipboard Toggle word wrap
3. Enter the absolute path for the zip file to export saved reports to, and press Enter:

   Filename to export saved reports to: /tmp/saved-reports.zip

   Copy to Clipboard Toggle word wrap
4. Copy the zip file to the new Reports machine:

   # scp /tmp/saved-reports.zip reports-machine-fqdn:/tmp/

   Copy to Clipboard Toggle word wrap
5. On the new Reports machine, run the ovirt-engine-reports-tool command:

   # ovirt-engine-reports-tool
   

   Copy to Clipboard Toggle word wrap
6. Enter the number that corresponds to the import option, and press Enter:

   (3) Import a saved reports zip file to Jasperreports
   (1, 2, 3) []: 3

   Copy to Clipboard Toggle word wrap
7. Enter the absolute path of the zip file from which to import, and press Enter:

   Filename to import saved reports from: /tmp/saved-reports.zip

   Copy to Clipboard Toggle word wrap

Procedure 1.16. Step 3: Removing the Reports Service from the Manager Machine

1. Stop the Reports service:

   # service ovirt-engine-reportsd stop

   Copy to Clipboard Toggle word wrap
2. Remove the Reports package:

   # yum remove rhevm-reports

   Copy to Clipboard Toggle word wrap
3. Remove the Reports files:

   # rm -rf /etc/ovirt-engine-reports /var/lib/ovirt-engine-reports

   Copy to Clipboard Toggle word wrap
4. Remove the Reports database and user. The default name for both is ovirt_engine_reports:

   # su - postgres
   $ psql
   postgres=# drop database ovirt_engine_reports;
   postgres=# drop user ovirt_engine_reports;
   

   Copy to Clipboard Toggle word wrap