Bug 1438080
| Summary: | Grafton DNS and DHCP requirements | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | joherr |
| Component: | Documentation | Assignee: | Laura Bailey <lbailey> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | SATHEESARAN <sasundar> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rhgs-3.2 | CC: | asriram, joherr, rhs-bugs, sankarshan, sasundar, storage-doc, storage-qa-internal |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-29 04:10:59 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: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1277939, 1451861 | ||
John, What is the reason for having client network IP in /etc/hosts file, When we say DNS is required to resolve each deployed hosts as well as the engine FQDN. Is it just to easily represent the hostname ? With our test environment: 1. We have both front-end network IP and back-end network IP with assigned FQDN ( fully resolvable ) 2. In some setups, we have only back-end network IP assigned with FQDN. In those cases we directly make use of IP itself. So, having the client network IP with the FQDN or with IP could completely depend up on the users. I think we should not add this particular info to add IP to /etc/hosts, but rest of other information is required. What do you think ? Sorry for the late response, I replied to the bug email and thought it would update this.
Response:
What is the reason for having client network IP in /etc/hosts file,
When we say DNS is required to resolve each deployed hosts as well as the engine FQDN. Is it just to easily represent the hostname ?
I appologize. I dont know why I could not get this working without adding
it to the /etc/hosts file as well. I retried without it in the /etc/hosts
file and just having the ovirt/public network resolve via DNS and it works
fine.
So this does not need to be in the /etc/hosts file.
...
What do you think ?
I agree.
Verified that the changes are available in the doc Fixed in RHGS 3.3 documentation. |
Document URL: https://doc-stage.usersys.redhat.com/documentation/en-us/red_hat_gluster_storage/3.2/html-single/deploying_red_hats_hyper-converged_infrastructure/ Its also in the article on access.redhat.com: https://access.redhat.com/articles/2922421#c-automatically-set-up-storage-and-install-hosted-engine-7 Section Number and Name: Describe the issue: The document doe snot mention Name resolution or DHCP requirements, but when deploying it is needed. Suggestions for improvement: Mention that each host deployed must have a FQDN entry for its client network IP in the /etc/hosts file Mention that DNS is required to resolve each deployed hosts FQDN as well as the engines FQDN. Mention that a DHCP server will be needed if choosing DHCP for the Engine VM network configuration. Additional information: