Bug 1387646

Summary: [Doc] How to access engine not only by engine FQDN but also using alternate host names
Product: Red Hat Enterprise Virtualization Manager Reporter: daniel <dmoessne>
Component: DocumentationAssignee: rhev-docs <rhev-docs>
Status: CLOSED DUPLICATE QA Contact: rhev-docs <rhev-docs>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.0.1CC: lbopf, lsurette, mtessun, rbalakri, Rhev-m-bugs, srevivo, ykaul, ylavi
Target Milestone: ovirt-4.1.1   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-12 06:16:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Docs RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description daniel 2016-10-21 12:38:36 UTC
Description of problem:
in bz 1376329 we provide a solution how to access engine not only by engine FQDN but also using alternate host names.
This feature should also be documented downstream.


Version-Release number of selected component (if applicable):
RHV4


How reproducible:
n/a


Steps to Reproduce:
n/a

Actual results:
not documented how to use that feature in Red Hat docs


Expected results:
Find in documentation how to use that feture


Additional info:

from https://bugzilla.redhat.com/show_bug.cgi?id=1325746 :
Engine can be accessed using alternate host names (or IP addresses) that can configured by adding a new configuration file (for example /etc/ovirt-engine/engine.conf.d/99-custom-sso-setup.conf) with following content:

SSO_ALTERNATE_ENGINE_FQDNS="alias1.example.com alias2.example.com"

The list of alternate names has to be listed separated by spaces.

It's possible to add also IP addresses of engine host, but using IP addresses instead of DNS names is not considered to be a good practise.

Comment 1 Lucy Bopf 2017-05-12 06:16:23 UTC
This was covered in bug 1431721. Closing this one as a duplicate.

*** This bug has been marked as a duplicate of bug 1431721 ***