Bug 1139793
| Summary: | [RFE] Keep hosted engine VM configuration in the shared storage | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Doron Fediuck <dfediuck> | |
| Component: | ovirt-hosted-engine-setup | Assignee: | Simone Tiraboschi <stirabos> | |
| Status: | CLOSED ERRATA | QA Contact: | Elad <ebenahar> | |
| Severity: | low | Docs Contact: | ||
| Priority: | medium | |||
| Version: | unspecified | CC: | acanan, dfediuck, gklein, iheim, juwu, lbopf, nsednev, pstehlik, rgolan, sbonazzo, sherold, ykaul, ylavi | |
| Target Milestone: | ovirt-3.6.0-rc | Keywords: | FutureFeature | |
| Target Release: | 3.6.0 | Flags: | sherold:
Triaged+
ylavi: testing_beta_priority+ |
|
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Enhancement | ||
| Doc Text: |
Previously, every host in a self-hosted engine environment stored a configuration file for the self-hosted engine virtual machine. As a result, any change to the configuration required users to update the file on each host. Now, a single self-hosted engine configuration file is saved on shared storage, and can be accessed by all hosts.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1139795 (view as bug list) | Environment: | ||
| Last Closed: | 2016-03-09 18:52:12 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | Integration | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 1269768 | |||
| Bug Blocks: | 1139795, 1167262, 1234915 | |||
|
Description
Doron Fediuck
2014-09-09 15:59:40 UTC
(In reply to Doron Fediuck from comment #0) > Description of problem: > Currently every host has a configuration file for the hosted engine VM. > If a change is needed files in all hosts should be fixed. > > So we should be storing a single file in a shared storage to simplify it. Hi Doron, Should this require from us to use shared storage at all times for HE, thus turning shared storage to basic requirement for the deployment? (In reply to Nikolai Sednev from comment #1) > (In reply to Doron Fediuck from comment #0) > > Description of problem: > > Currently every host has a configuration file for the hosted engine VM. > > If a change is needed files in all hosts should be fixed. > > > > So we should be storing a single file in a shared storage to simplify it. > > Hi Doron, > Should this require from us to use shared storage at all times for HE, thus > turning shared storage to basic requirement for the deployment? the requirement already exist today: we create a DC, domain and disks for the engine-vm. NFS,glusgter,iscsi, we see them all as non-local. our goal is to alleviate ovirt's backup of vms in special disks for shared configuration for both the VM and the broker conf Hosted engine VM configuration is being saved on the shared storage. Executed hosted engine sanity over all supported storage types (NFS, iSCSI, Gluster, FC) to check there are no regressions, all passed. In addition, checked that the configuration exist in the shared storage under /rhev/data-center/pool/HE-SD/conf-img/ The following files are saved there: vm.conf, version, fhanswers.conf, hosted-engine.conf, broker.conf Tested using: vdsm-jsonrpc-4.17.18-0.el7ev.noarch vdsm-python-4.17.18-0.el7ev.noarch vdsm-hook-vmfex-dev-4.17.18-0.el7ev.noarch vdsm-cli-4.17.18-0.el7ev.noarch vdsm-yajsonrpc-4.17.18-0.el7ev.noarch vdsm-xmlrpc-4.17.18-0.el7ev.noarch vdsm-4.17.18-0.el7ev.noarch vdsm-infra-4.17.18-0.el7ev.noarch ovirt-hosted-engine-ha-1.3.3.7-1.el7ev.noarch libgovirt-0.3.3-1.el7_2.1.x86_64 ovirt-vmconsole-1.0.0-1.el7ev.noarch ovirt-host-deploy-1.4.1-1.el7ev.noarch ovirt-setup-lib-1.0.1-1.el7ev.noarch ovirt-vmconsole-host-1.0.0-1.el7ev.noarch ovirt-hosted-engine-setup-1.3.2.3-1.el7ev.noarch 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-2016-0375.html |