Bug 1332703 - [DOC] Incorrect arcitecture examples in OpenStack 8 architecture guide
Summary: [DOC] Incorrect arcitecture examples in OpenStack 8 architecture guide
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 8.0 (Liberty)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Documentation Team
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-03 20:44 UTC by jliberma@redhat.com
Modified: 2020-01-07 18:38 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Chapter 4 of the OpenStack Architecture guide is misleading because most of the designs include features that are not supported / tech preview / or cannot be deployed by OSP director.
Clone Of:
Environment:
Last Closed: 2020-01-07 18:38:40 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description jliberma@redhat.com 2016-05-03 20:44:14 UTC
https://access.redhat.com/documentation/en/red-hat-openstack-platform/8/architecture-guide/chapter-4-architecture-examples

Chapter 4 of the OpenStack Architecture guide is misleading because most of the designs include features that are not supported / tech preview / or cannot be deployed by OSP director.

A few examples:
- Nova cells
- Trove
- Object storage gateway servers on distinct nodes from the OpenStack controllers
- etc.

Ideally the document should be corrected to align with our recommended architecture as deployed by OSP director.

If that is not possible language should be added that these are generic OpenStack recommendations that do not imply support by Red Hat.

If neither is possible the document should be pulled. 

Re-branding upstream documents as Red Hat documents is a bad practice generally because the upstream documents can include features and designs that we do not recommend, have not tested, cannot provide, or do not support.


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