Bug 975641 - Create Object Storage Architecture Diagram
Summary: Create Object Storage Architecture Diagram
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: doc-Installation_and_Configuration_Guide
Version: 3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 3.0
Assignee: Summer Long
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks: 889481
TreeView+ depends on / blocked
 
Reported: 2013-06-19 02:19 UTC by Summer Long
Modified: 2014-02-28 04:28 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-01 20:24:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Summer Long 2013-06-19 02:19:49 UTC
Description of problem: A diagram is required. Use and rebrand subset of:

http://docs.openstack.org/trunk/openstack-compute/admin/content/logical-architecture.html


Version-Release number of selected component (if applicable):
3.0

Expected results:
Create a new diagram
Place into Object Storage Install/Configuration chapter with appropriate text.



Document URL: 

Section Number and Name: 

Describe the issue: 

Suggestions for improvement: 

Additional information:

Comment 5 Summer Long 2013-06-24 01:02:07 UTC
The section 6.5.5 comments have been dealt with in 959503.

The diagram has been updated, with review by Pete:
> I've reworked the diagram. Let me know what you think?
> Note: I've kept the bi-directional arrows, since this is the diagram 
> convention so far...shows traffic flow.  Am including the arch overview 
> diagram for comparison.

The diagram looks better now. I still do not agree with bidirectional
arrows, but even so now it's helpful in understanding the parts.
Greetings,
-- Pete
======================================
Diagram with text has been placed back into: 
6.2.  Architecture of the Object Storage Service
==================================================
Ready for QE with the next doc release.


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