Description of problem:
It should be possible to install and use engine-backup on dwh/reports when they are set up on separate machines.
The code basically allows that.
Main issue is that its currently packaged inside the -tools package, which requires the engine. Need to think if we can drop this dep.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Needed for migration from el6 to el7
Why did you move this?
How will be backup dwh on el6 before moving it to el7?
Bug cloned to 3.6 since the solution will differ between 4.0 and 3.6.
yum deplist ovirt-engine-tools-backup
Loaded plugins: product-id, search-disabled-repos, versionlock
package: ovirt-engine-tools-backup.noarch 220.127.116.11-0.1.el7ev
provider: bash.x86_64 4.2.46-19.el7
provider: bzip2.x86_64 1.0.6-13.el7
dependency: otopi >= 1.5.0
provider: otopi.noarch 1.5.0-3.el7ev
dependency: ovirt-engine-setup-plugin-ovirt-engine-common >= 18.104.22.168-0.1.el7ev
provider: ovirt-engine-setup-plugin-ovirt-engine-common.noarch 22.214.171.124-0.1.el7ev
dependency: postgresql >= 8.4.7
provider: postgresql.x86_64 9.2.15-1.el7_2
provider: postgresql.i686 9.2.13-1.el7_1
provider: tar.x86_64 2:1.26-29.el7
provider: xz.x86_64 5.1.2-12alpha.el7
oVirt 4.0.0 has been released, closing current release.