Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1214195

Summary: [Docs] [Installer] The network topology diagram is misleading
Product: Red Hat OpenStack Reporter: David Juran <djuran>
Component: documentationAssignee: Dan Macpherson <dmacpher>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0 (Juno)CC: adahms, djuran, sputhenp, yeylon
Target Milestone: ---Keywords: Documentation, ZStream
Target Release: 6.0 (Juno)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-21 04:20:08 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: 1277361    

Description David Juran 2015-04-22 08:40:49 UTC
Description of problem:
The diagram on https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/6/html/Installer_and_Foreman_Guide/chap-Planning_your_Environment.html suggest that "external" network type can be mixed with the "public" network type (red and yellow network). The StayPuft installer however does not allow this.

Comment 3 Andrew Dahms 2015-04-23 00:21:18 UTC
Assigning to Dan for review.

Comment 4 Dan Macpherson 2015-06-02 04:06:53 UTC
I think this might be confusion between how OpenStack "public" and "external" -- or at least, some people might think they're the same thing.

David, are you okay with removing "public" from the image? Would that be more accurate?

Comment 5 David Juran 2015-06-04 11:13:43 UTC
No, there still need to be a Public API network. And the RHEL OSP installer doesn't allow you to place it on the same network as the External, i.e. the one where the floating IP:s etc will be created

Comment 6 Dan Macpherson 2015-06-04 18:16:04 UTC
Hey David,

If my understanding is correct though, the Public API network can be assigned to the management network (and that's actually the default when you first configure the network settings). And for customers looking to expose the Public API on its own network can do so by following this article: https://access.redhat.com/articles/1433703

So, it seems that the Public API is still covered under the management network, which explains my reasoning of just removing the word "public" from the external network.

- Dan

Comment 7 David Juran 2015-06-11 10:54:02 UTC
This _should_ be possible but won't work due to bug 1176423

Comment 8 Dan Macpherson 2015-06-12 05:47:16 UTC
Hi David,

Ah, I understand why now. Thanks.

I'm revising the deployment scenarios at the moment, so I'll include this diagram as part of my revision.

Also, directing customer case to this bug too.

Comment 9 Dan Macpherson 2015-06-12 05:48:33 UTC
*** Bug 1227009 has been marked as a duplicate of this bug. ***

Comment 22 Dan Macpherson 2015-10-21 04:20:08 UTC
So this image has been updated and pushed live for a while now:

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/6/html/Installer_and_Foreman_Guide/chap-Planning_your_Environment.html

Closing this bug, but feel free to reopen if further changes are needed.