Bug 1983171 - [RFE] Option to configure static domains for RHV hypervisors
Summary: [RFE] Option to configure static domains for RHV hypervisors
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 4.4.6
Hardware: All
OS: Linux
high
medium
Target Milestone: ---
: ---
Assignee: rhev-docs@redhat.com
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On: 1984277
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-16 17:39 UTC by Allie DeVolder
Modified: 2022-08-07 12:24 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-23 10:20:47 UTC
oVirt Team: Network
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Allie DeVolder 2021-07-16 17:39:40 UTC
1. What is the nature and description of the request?
      Customer needs to be able to configure a static search domain on RHV hypervisors. This is currently not available as a hypervisor network configuration option. Customer is currently manually modifying ifcfg-scripts and manually adding entries to resolv.conf.

   2. Why does the customer need this? (List the business requirements here)
      Customer's infrastructure requires this, and the change may not be persistant across updates or modifications.

   3. How would the customer like to achieve this? (List the functional
requirements here)
      Add static search domains to the network configuration options that would update resolv.conf on hosts with those entries.

Comment 2 Ales Musil 2021-07-21 06:31:17 UTC
Hi,

adding this option to RHV manager and then to vdsm would require a lot of effort. 

There is an option to write a custom vdsm hook. Applying it through nmstate as we do 
for custom static routes is not possible as nmstate is not supporting that currently.

Comment 3 ctomasko 2022-02-11 21:04:13 UTC
Bug triage. This bug is blocked by https://bugzilla.redhat.com/show_bug.cgi?id=1984277. The docs team will keep the target milestone as ovirt 4.5.0 for monitoring purposes only. We won't commit to the bug fix until the blocked-by issue is resolved.

Comment 5 Marina Kalinin 2022-03-29 23:39:54 UTC
After reviewing this request, we have decided to not implement it at this time.


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