Bug 1247286
Summary: | rhos-d uses non-RFC1918 address schemes, possible external conflicts | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Will Foster <wfoster> | ||||
Component: | rhosp-director | Assignee: | Hugh Brock <hbrock> | ||||
Status: | CLOSED WONTFIX | QA Contact: | Shai Revivo <srevivo> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | Director | CC: | dsneddon, jcoufal, mburns, rhel-osp-director-maint | ||||
Target Milestone: | --- | ||||||
Target Release: | 10.0 (Newton) | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2016-10-14 20:38:13 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: | |||||||
Attachments: |
|
Description
Will Foster
2015-07-27 17:44:14 UTC
Adding, 192.0.2 is reserved via IANA as a "testnet" used for documentation. http://tools.ietf.org/html/rfc5737 192.0.2.0/24 TEST-NET-1 RFC 5737 "The blocks 192.0.2.0/24 (TEST-NET-1), 198.51.100.0/24 (TEST-NET-2), and 203.0.113.0/24 (TEST-NET-3) are provided for use in documentation." For undercloud deployments or internal purposes this type of range shouldn't be used, we should stick to RFC1918 allotment. Created attachment 1056693 [details]
Attached: Example undercloud.conf.sample shipped
Attaching undercloud.conf.sample used with 192.0.2.x addressing scheme.
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10. (In reply to Will Foster from comment #4) > Created attachment 1056693 [details] > Attached: Example undercloud.conf.sample shipped > > Attaching undercloud.conf.sample used with 192.0.2.x addressing scheme. I disagree that we are misusing the network 192.0.2.x as the default in our ctlplane configuration. The whole reason this range was chosen is that it is for documentation and examples. We definitively do not want people deploying in production with 192.0.2.x, so the default is actually intended to encourage people to choose their own subnet. Perhaps we could do a better job documenting that. This is in contrast to the isolated networks, where we chose 172. addresses specifically to indicate that they are private, and the defaults may be used as-is. If there were a similar "example" network available that would be a good fit for the External network default (currently 10.0.0.0/24), I would prefer to use that, because this is another network that we intend for people to customize. |