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

# Separate DWH Host

### Summary

Allow ovirt-engine-dwh to be installed and configured by engine-setup on a separate machine, without requiring ovirt-engine 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. We assume that user wants to install dwh on machine B.

We need access to the engine's database. If on separate host, user will be prompted for them.

We need to also fix bug <https://bugzilla.redhat.com/1059283> - check minimal ETL version, as we'll not be able to rely on package dependencies anymore.

# Migrating an existing DWH and Reports installation

For migration of an existing installation of DWH and Report to a different server please refer to:

# Migrating an existing DWH and Reports

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

### Benefit to oVirt

DWH sometimes causes a significant load on the engine machine. Installing it on a separate machine will allow distributing the load.

### Dependencies / Related Features

### Documentation / External references<commit_msg>Migrating an existing DWH and Reports installation<commit_after>---
title: Separate-DWH-Host
category: feature
authors: didi, sandrobonazzola, sradco
wiki_category: Feature|Separate DWH Host
wiki_title: Features/Separate-DWH-Host
wiki_revision_count: 16
wiki_last_updated: 2015-01-16
feature_name: Separate DWH Host
feature_modules: engine
feature_status: Design
---

# Separate DWH Host

### Summary

Allow ovirt-engine-dwh to be installed and configured by engine-setup on a separate machine, without requiring ovirt-engine 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. We assume that user wants to install dwh on machine B.

We need access to the engine's database. If on separate host, user will be prompted for them.

We need to also fix bug <https://bugzilla.redhat.com/1059283> - check minimal ETL version, as we'll not be able to rely on package dependencies anymore.

# 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:

# Migrating an existing DWH and Reports

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

### Benefit to oVirt

DWH sometimes causes a significant load on the engine machine. Installing it on a separate machine will allow distributing the load.

### Dependencies / Related Features

### Documentation / External references
{'fraction_non_alphanumeric': 0.06769416742218193, 'fraction_numerical': 0.011483831973405863, 'mean_word_length': 4.610169491525424, 'pattern_counts': {'":': 0, '<': 11, '<?xml version=': 0, '>': 11, 'https://': 2, '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': '1070453', 'n_tokens_mistral': 970, 'n_tokens_neox': 912, 'n_words': 422}