Bug 1782412 - [RFE] RHV+Metrics Store - Support a Flat DNS environment without subdomains
Summary: [RFE] RHV+Metrics Store - Support a Flat DNS environment without subdomains
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-metrics
Version: 4.3.6
Hardware: All
OS: Linux
medium
high
Target Milestone: ovirt-4.3.8
: 4.3.8
Assignee: Shirly Radco
QA Contact: Guilherme Santos
URL:
Whiteboard:
: 1782514 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-11 15:17 UTC by Robert McSwain
Modified: 2023-09-07 21:14 UTC (History)
5 users (show)

Fixed In Version: ovirt-engine-metrics-1.3.6.1
Doc Type: Enhancement
Doc Text:
In the current release, Metrics Store adds support for a flat DNS environment without subdomains. This capability helps you satisfy security policies that mandate having a "flat" DNS environment with no submains. To enable this capability, you add a suffix to the master0 virtual machine when you configure networking for Metrics Store virtual machines. For example, if you set 'openshift_ovirt_machine_suffix' to 'prod' and 'public_hosted_zone' is 'example.com', then the metrics store virtual machine will be called 'master-prod0.example.com'.
Clone Of:
Environment:
Last Closed: 2020-02-13 15:24:42 UTC
oVirt Team: Metrics
Target Upstream Version:
Embargoed:
lsvaty: testing_plan_complete-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-47491 0 None None None 2022-07-09 15:10:31 UTC
Red Hat Product Errata RHSA-2020:0498 0 None None None 2020-02-13 15:24:54 UTC
oVirt gerrit 105990 0 master MERGED Allow flat DNS name to metrics store vms 2020-02-24 08:36:50 UTC
oVirt gerrit 106106 0 ovirt-engine-metrics-4.3 MERGED Allow flat DNS name to metrics store vms 2020-02-24 08:36:50 UTC
oVirt gerrit 106108 0 ovirt-engine-metrics-4.3 MERGED Fix additional issues for flat dns support 2020-02-24 08:36:50 UTC
oVirt gerrit 106111 0 ovirt-engine-metrics-4.3 MERGED Fix additional issues for flat dns support 2020-02-24 08:36:50 UTC

Description Robert McSwain 2019-12-11 15:17:50 UTC
Description of problem:
Security policy mandates that we maintain a "flat" DNS environment -- no submains.  Components of the RHV 4.3 Metrics Store installation require subdomains.  However, code can be altered to support custom host names that support a "flat" DNS environment.

Version-Release number of selected component (if applicable):
RHV 4.3/4.4

Expected Behavior:
RHV will support not using subdomains for use in a "flat" DNS environment 

Actual Behavior:
Currently RHV and Metrics Store require DNS subdomains.

Comment 1 Shirly Radco 2020-01-05 12:11:43 UTC
This fix adds an option to add a suffix to master0 VM.

Example:
If user sets 'openshift_ovirt_machine_suffix' to 'prod' and
'public_hosted_zone' is 'example.com',
Then the metrics store vm will be called 'master-prod0.example.com'.

Comment 3 Shirly Radco 2020-01-09 14:12:25 UTC
*** Bug 1782514 has been marked as a duplicate of this bug. ***

Comment 4 Guilherme Santos 2020-01-15 15:58:01 UTC
Verified on:
ovirt-engine-metrics-1.3.6.2-1.el7ev.noarch

Steps:
1. Followed metrics installation tutorial until step 4 (https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html/metrics_store_installation_guide/installing_metrics_store#Creating_the_metrics_store_virtual_machines)
2. Added 'openshift_ovirt_machine_suffix' variable to 'test' on metrics-store-config.yml
3. Filled the 'public_hosted_zone' as redhat.com
4. Continued with the tutorial until the step to run the ovirt-metrics-store-installation playbook to create the virtual machines
(included)
5. On the engine, checked the new created VMs
6. Finished deployment of metrics (according with tutorial)
7. Checked Kibana discovery tab

Results:
5. master0 vm created successfully with its name as master-test0.redhat.com
7. metrics fully working as expected

Comment 9 errata-xmlrpc 2020-02-13 15:24:42 UTC
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://access.redhat.com/errata/RHSA-2020:0498


Note You need to log in before you can comment on or make changes to this bug.