Proposed title of this feature request
Do not support running RHEV's primary/secondary DNS servers from within RHEV itself
What is the nature and description of the request?
RHEV relies heavily on DNS for communication. When RHEV is configured to use a primary DNS server that is hosted within RHEV problems can occur. For example, if the primary DNS server goes down within RHEV, RHEV loses the ability to query hypervisors for VM status. Even when there is a secondary DNS server, overall engine performance is greatly inhibited. Moreover, in the event that there is only one DNS server, the customer might find themselves in a situation where hypervisors go unresponsive because they can no longer resolve the manager, making it impossible to bring the DNS server back online.
We should strongly discourage (or even better officially not support) running RHEV's DNS servers from within RHEV itself.
Why does the customer need this? (List the business requirements here)
Customers do not realize the negative implications of this configuration.
How would the customer like to achieve this? (List the functional requirements here)
Documentation warning against it.
For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
We need to make this clear in the same manner with which we state we do not support running RHEV on the same machine as IPA
Is there already an existing RFE upstream or in Red Hat Bugzilla?
Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
No, but the sooner the better.
Is the sales team involved in this request and do they have any additional input?
List any affected packages or components.
Online RHEV documentation
Would the customer be able to assist in testing this functionality if implemented?
They could verify that the warning exists.
Thanks James! That would be great!
Since the note is acked by the original bug requester, moving this bug to VERIFIED. Aiming to publish the content for the 3.6 Beta release.