+++ This bug was initially created as a clone of Bug #1122583 +++ Description of problem: For OSP deployments some networks require DNS service to be provided Version-Release number of selected component (if applicable): N/A How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This real requirement for provioner network. Under Customer/deployer control which other networks need DNS.
The RHEL-OSP installer currently runs only on RHEL 6. Changes made on RHEL 6 will apply to RHEL-OSP deployments on both RHEL 6 and RHEL 7. Closing this bug as a duplicate since we only need to track it in 1 place. *** This bug has been marked as a duplicate of bug 1122583 ***
We don't need Foreman server to provide DHCP for all of the separate networks (Storage, Management, APIs, Tenant). The two options will be for Foreman to statically assign addresses out of a pool (specified by a range) or for the existing infrastructure to have its own DHCP server. However... We can't expect DNS to be provided in the case where static addressing is used, so Foreman will need to run a DNS server that covers all of the different networks so we have proper resolution for all nodes' interfaces. It's unclear as to whether or not this is a definite need or a nice to have. We need info from the Ceph team to figure out if DNS resolvability is a requirement for their software.
Updating title based on comment 4
setting up and managing DNS is outside the scope of this request based on comment 4. We'll assume that a DNS service exist on the network.
Verified: rhel-osp-installer-0.4.1-2.el6ost.noarch We now have the ability to specify how the IP is provided/assigned per network. The options are: None (means external DHCP is used) DHCP (foreman actually manages the DHCP) Internal DB (means the admin has to provide a range of addresses, the bootmode of the NIC should be set to static)
testonly, feature existed in A1, no doc text needed
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/RHBA-2014-1800.html