Bug 1079351
Summary: | [rhevm-dwh-setup] Enable specifying a different DB server than the engine DB server | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Jiri Belka <jbelka> |
Component: | ovirt-engine-dwh | Assignee: | Yedidyah Bar David <didi> |
Status: | CLOSED ERRATA | QA Contact: | Pavel Novotny <pnovotny> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.3.0 | CC: | dfediuck, gklein, iheim, juwu, lnovich, movciari, rbalakri, Rhev-m-bugs, sherold, talayan, yeylon, ylavi |
Target Milestone: | --- | ||
Target Release: | 3.5.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | integration | ||
Fixed In Version: | oVirt Beta2 | Doc Type: | Bug Fix |
Doc Text: |
Previously, when using a remote database, the ovirt-engine-dwh-setup configured the host and engine databases on the same machine, and it was not possible to specify a different database host. In Red Hat Enterprise Virtualization 3.4, the DWH setup utility was replaced with a plug-in to use the common engine-setup utility and made it possible to input a database host as needed when setting up DWH with a remote database. This feature was a Tech Preview feature in Red Hat Enterprise Virtualization 3.4, and now a supported feature in 3.5.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2015-02-11 18:14:45 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1080997, 1100200, 1142923, 1156165 |
Description
Jiri Belka
2014-03-21 13:00:29 UTC
No supported for 3.4. will consider this for 3.5. Yaniv Should be in for 3.5. Please test this. Yaniv Of course in first 3.5 release. Yaniv Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2015-0177.html |