Red Hat Bugzilla – Bug 1156015
Upgrade procedure of Reports from local setup to remote
Last modified: 2015-09-22 09:10 EDT
+++ This bug was initially created as a clone of Bug #1156009 +++ Description of problem: The should be a wiki for upgrade procedure of Reports from local setup to remote. Version-Release number of selected component (if applicable): 3.5
Overview of the process: Start with a 3.5 engine/dwh/reports setup on a single host (from clean or upgraded) * service ovirt-engine-reportsd stop * Keep somewhere the db credentials (can be found at /var/lib/ovirt-engine-reports/build-conf/master.properties) * yum remove ovirt-engine-reports (or rhevm-reports) On the new reports machine: * yum install ovirt-engine-reports * engine-setup - supply existing credentials I didn't try that myself. As discussed, if you do not care about the data in the reports db, you can simply setup a new machine with a new db - in principle there can be more than one reports server.
This process was not tested fully and should be tested.
I tried it and it works. The process for this should be : Start with a 3.5 engine/dwh/reports setup on a single host (from clean or upgraded) After the engine and dwh are setup successfully. On the new reports machine: * yum install ovirt-engine-reports * engine-setup - supply existing credentials DWH credentials are located at /etc/ovirt-engine-dwh/ovirt-engine-dwhd.conf.d/10-setup-database.conf On the engine machine: If the user wants to remove the other reports installation * "Saved Reports" can be migrated to the new installation ,by following the steps of export and import saved reports, according to the documentations . Only after that run on the old machine: * service ovirt-engine-reportsd stop * yum remove ovirt-engine-reports (or rhevm-reports)
Important! There may be more than one reports instance. And they will all show the reports. But, The engine will direct to and have SSO with only with the last reports instance that run engine-setup.
What is the status of this?
SME Review already done and vaild. New section added here Topics 42376, 42377, 42378 http://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.5/html/Administration_Guide/sect-Migrating_to_a_remote_machine.html#Migrating_the_Reports_to_a_Remote_Machine What changed: New section was added describing how to migrate the Reports to a remote machine.
Moving this bug back to assigned while I work on this content.
Included in the latest async release.