<commit_before>---
title: Separate-Reports-Host
category: feature
authors: didi, sandrobonazzola, sradco
wiki_category: Feature|Separate Reports Host
wiki_title: Features/Separate-Reports-Host
wiki_revision_count: 20
wiki_last_updated: 2015-01-16
feature_name: Separate Reports Host
feature_modules: engine
feature_status: QE
---

# Separate Reports Host

# Summary

Allow ovirt-engine-reports to be installed and configured by engine-setup on a separate machine, without requiring ovirt-engine or DWH to be on the same host.

# Owner

*   Name: [ Didi](User:Didi)

<!-- -->

*   Email: <<EMAIL>>

# Current status

Implemented, should be available in 3.5.

# Detailed Description

We assume that engine is already setup and running on machine A.

If dwh is already installed and setup on machine B (can be same as A), and user wants to install reports on machine C, we need access to the engine's database and to dwh's database. If on separate host, user will be prompted for them.

If dwh is to be setup on machine B and user wants to install reports on the same machine B, we already have the credentials.

If dwh and reports are to be setup together on machine B, we need to make sure that setup recognizes that somehow, so that the reports plugin has access to needed info. Perhaps we'll decide to postpone that option - if we do, user will have to first setup dwh then reports.

# Migrating an existing DWH and Reports installation

For migration of an existing local installation of DWH and Report to a different server please refer to [Migration_of_DWH&Reports](Features/Migration_of_DWH&Reports)

# Example setup

Three VMs were created with fedora 19 installed. They are named 'f19-2' (for the engine), 'f19-2-dwh' (for DWH) and 'f19-2-reports' (for Reports).

### Engine

Let's start by setting up the engine on the engine machine:

      [root@didi-f19-2 ~]# engine-setup
      [ INFO  ] Stage: Initializing
      [ INFO  ] Stage: Environment setup
                Configuration files: ['/etc/ovirt-engine-setup.conf.d/10-packaging.conf']
                Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20140804123130-0uuwlt.log
                Version: otopi-1.3.0_master (otopi-1.3.0-0.0.master.20140715.git336a22e.fc19)
      [ INFO  ] Stage: Environment packages setup
      [ INFO  ] Stage: Programs detection
      [ INFO  ] Stage: Environment setup
      [ INFO  ] Stage: Environment customization
                --== PRODUCT OPTIONS ==--
                Configure Engine on this host (Yes, No) [Yes]:
                Configure Data Warehouse on this host (Yes, No) [Yes]: no
                Configure Reports on this host (Yes, No) [Yes]: no
                Configure WebSocket Proxy on this host (Yes, No) [Yes]:

All components were installed with yum, so we can choose which to enable. If we do not install dwh/reports we'll not be asked about them.

                --== PACKAGES ==--
      [ INFO  ] Checking for product updates...
      [ INFO  ] No product updates found
                --== ALL IN ONE CONFIGURATION ==--<commit_msg>Migrating an existing DWH and Reports installation<commit_after>---
title: Separate-Reports-Host
category: feature
authors: didi, sandrobonazzola, sradco
wiki_category: Feature|Separate Reports Host
wiki_title: Features/Separate-Reports-Host
wiki_revision_count: 20
wiki_last_updated: 2015-01-16
feature_name: Separate Reports Host
feature_modules: engine
feature_status: QE
---

# Separate Reports Host

# Summary

Allow ovirt-engine-reports to be installed and configured by engine-setup on a separate machine, without requiring ovirt-engine or DWH to be on the same host.

# Owner

*   Name: [ Didi](User:Didi)

<!-- -->

*   Email: <<EMAIL>>

# Current status

Implemented, should be available in 3.5.

# Detailed Description

We assume that engine is already setup and running on machine A.

If dwh is already installed and setup on machine B (can be same as A), and user wants to install reports on machine C, we need access to the engine's database and to dwh's database. If on separate host, user will be prompted for them.

If dwh is to be setup on machine B and user wants to install reports on the same machine B, we already have the credentials.

If dwh and reports are to be setup together on machine B, we need to make sure that setup recognizes that somehow, so that the reports plugin has access to needed info. Perhaps we'll decide to postpone that option - if we do, user will have to first setup dwh then reports.

# Migrating an existing DWH and Reports installation

For migration of an existing local installation of DWH and Report to a different server please refer to [Migration_of_local_DWH_Reports_to_remote](Features/Migration_of_local_DWH_Reports_to_remote)

# Example setup

Three VMs were created with fedora 19 installed. They are named 'f19-2' (for the engine), 'f19-2-dwh' (for DWH) and 'f19-2-reports' (for Reports).

### Engine

Let's start by setting up the engine on the engine machine:

      [root@didi-f19-2 ~]# engine-setup
      [ INFO  ] Stage: Initializing
      [ INFO  ] Stage: Environment setup
                Configuration files: ['/etc/ovirt-engine-setup.conf.d/10-packaging.conf']
                Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20140804123130-0uuwlt.log
                Version: otopi-1.3.0_master (otopi-1.3.0-0.0.master.20140715.git336a22e.fc19)
      [ INFO  ] Stage: Environment packages setup
      [ INFO  ] Stage: Programs detection
      [ INFO  ] Stage: Environment setup
      [ INFO  ] Stage: Environment customization
                --== PRODUCT OPTIONS ==--
                Configure Engine on this host (Yes, No) [Yes]:
                Configure Data Warehouse on this host (Yes, No) [Yes]: no
                Configure Reports on this host (Yes, No) [Yes]: no
                Configure WebSocket Proxy on this host (Yes, No) [Yes]:

All components were installed with yum, so we can choose which to enable. If we do not install dwh/reports we'll not be asked about them.

                --== PACKAGES ==--
      [ INFO  ] Checking for product updates...
      [ INFO  ] No product updates found
                --== ALL IN ONE CONFIGURATION ==--
{'fraction_non_alphanumeric': 0.07795136092768562, 'fraction_numerical': 0.021259462071186987, 'mean_word_length': 3.0882159315339037, 'pattern_counts': {'":': 0, '<': 9, '<?xml version=': 0, '>': 9, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6192334', 'n_tokens_mistral': 2079, 'n_tokens_neox': 1957, 'n_words': 762}