| Summary: | [Docs] [Director] Stated method of setting DNS does not work with net iso | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Ben Nemec <bnemec> |
| Component: | documentation | Assignee: | Dan Macpherson <dmacpher> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | RHOS Documentation Team <rhos-docs> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.0 (Kilo) | CC: | adahms, bnemec, yeylon |
| Target Milestone: | ga | Keywords: | Documentation |
| Target Release: | 8.0 (Liberty) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-04-13 04:46:54 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Ben Nemec
2016-01-19 21:12:51 UTC
Assigning to Dan for review. Hi Ben, The DnsServers param should be included in the network isolation example: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/7/html/Director_Installation_and_Usage/sect-Advanced-Scenario_3_Using_the_CLI_to_Create_an_Advanced_Overcloud_with_Ceph_Nodes.html#sect-Advanced-Isolating_all_Networks_into_VLANs See Section 6.3.6.2. Creating an Advanced Overcloud Network Environment File. Also, included in the following network params table: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/7/html/Director_Installation_and_Usage/appe-Network_Environment_Options.html Does that mean we can remove Section 3.8. Setting a Nameserver for the Overcloud (the one where we set the DNS on the ctlplane)? Hmm, yeah I hadn't noticed that DnsServers was included in the net-iso configs. Unfortunately it is still valid to set the nameserver as described in 3.8 when not using network isolation, which makes me wonder if we should just more explicitly mention there that network isolation has separate nameserver configuration options. Unless we're going to say we won't document the none net-iso configuration, which might be valid since that isn't a production-ready configuration. So I guess my main concern was that we have a top-level heading for setting the nameserver, but the method it describes doesn't work for the real-world deployment method, and the real-world method is kind of buried in a large number of other configuration parameters. I guess the simplest thing to do would be to just call out the DnsServers param in 3.8, which would avoid confusion for network isolation users and doesn't require us to take a stand on whether we document none net-iso. I don't know if that wishy-washy answer helps. Mostly this just makes me wish we didn't have two different configuration methods for nameservers. :-/ (In reply to Ben Nemec from comment #4) > I guess the simplest thing to do > would be to just call out the DnsServers param in 3.8, which would avoid > confusion for network isolation users and doesn't require us to take a stand > on whether we document none net-iso. This work for me. I'll implement this. This content is now live on the Customer Portal. Closing. |