Bug 1101297
Summary: | [RFE] Allow fully automatic deployment process for hosted-engine | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Artyom <alukiano> |
Component: | ovirt-hosted-engine-setup | Assignee: | Simone Tiraboschi <stirabos> |
Status: | CLOSED ERRATA | QA Contact: | Artyom <alukiano> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 3.4.0 | CC: | alukiano, asegundo, didi, gklein, iheim, istein, juwu, lbednar, sbonazzo, s.kieske, ylavi |
Target Milestone: | ovirt-3.6.0-rc | Keywords: | FutureFeature, Triaged |
Target Release: | 3.6.0 | Flags: | sherold:
Triaged+
|
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | ovirt-3.6.0-alpha1 | Doc Type: | Enhancement |
Doc Text: |
With this release, Self-Hosted Engine setup can be fully automated by using the RHEV-M Virtual Appliance and dynamically configuring it with cloud-init.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-03-09 18:51:07 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: | |||
Bug Blocks: | 1217106 |
Description
Artyom
2014-05-26 16:35:50 UTC
is this just for unattended setup for testing? (because for production deployments, the plan is to make this simpler via the hosted-engine guest image as described in https://bugzilla.redhat.com/show_bug.cgi?id=1103409#c2) It's about the interaction on the host, unrelated to the engine VM stuff. Currently this interaction can't be fully automatic. In principle it can be - we'll need to make the verification questions (OS is setup? engine is setup?) loop until success (probably with some timeout) (as well as making them answerable from the answer file). *** Bug 1186742 has been marked as a duplicate of this bug. *** 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 |