Bug 1332708 - [DOC][RFE] Add deployed architecture diagram to OpenStack director docs
Summary: [DOC][RFE] Add deployed architecture diagram to OpenStack director docs
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 8.0 (Liberty)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Dan Macpherson
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-03 21:05 UTC by jliberma@redhat.com
Modified: 2018-03-18 10:53 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-18 10:53:32 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description jliberma@redhat.com 2016-05-03 21:05:13 UTC
https://access.redhat.com/documentation/en/red-hat-openstack-platform/version-8/director-installation-and-usage/

Director installation document has two diagrams:
- a block diagram of server roles deployed by director
- a network isolation diagram

It would be very useful to add an architectural diagram that shows the complete advanced deployment.

It should include:
- servers roles + number of deployed servers
- networks and connections
- service placement

The idea is to visualize the advanced deployment described by the documentation. Customers could use the diagram as the starting point for design discussions.

Comment 2 jliberma@redhat.com 2016-05-12 16:10:19 UTC
Dan I have some starting point diagrams from the old refarch is you want them

Comment 3 Nir Yechiel 2018-03-18 10:53:32 UTC
Looking at the latest RHOSP doc, there has been a significant progress on the network diagrams showed and their level of details, see https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/12/html-single/director_installation_and_usage/index#sect-Networking_Requirements.

Please re-open this bug if you have any other suggestions or feedback to the current guide.


Note You need to log in before you can comment on or make changes to this bug.