openstack/openstack-manuals
Code Issues Proposed changes

Merge "Changes to section_object-storage-example-install-arch"

Browse Source
This commit is contained in:
Jenkins 2014-04-11 07:42:25 +00:00 committed by Gerrit Code Review
commit 9ee39ee7c8
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
doc/install-guide/object-storage/section_object-storage-example-install-arch.xml
View File

@ -3,33 +3,33 @@
xmlns="http://docbook.org/ns/docbook" xmlns="http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"> xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
<title>Example Object Storage installation architecture</title> <title>Example of Object Storage installation architecture</title>
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para>node. A host machine that runs one or more OpenStack <para>Node: A host machine that runs one or more OpenStack
Object Storage services.</para> Object Storage services.</para>
</listitem> </listitem>
<listitem> <listitem>
<para>Proxy node. Runs proxy services.</para> <para>Proxy node: Runs proxy services.</para>
</listitem> </listitem>
<listitem> <listitem>
<para>Storage node. Runs account, container, and object <para>Storage node: Runs account, container, and object
services. Contains the SQLite databases.</para> services. Contains the SQLite databases.</para>
</listitem> </listitem>
<listitem> <listitem>
<para>Ring. A set of mappings between OpenStack Object <para>Ring: A set of mappings between OpenStack Object
Storage data to physical devices.</para> Storage data to physical devices.</para>
</listitem> </listitem>
<listitem> <listitem>
<para>Replica. A copy of an object. By default, three <para>Replica: A copy of an object. By default, three
copies are maintained in the cluster.</para> copies are maintained in the cluster.</para>
</listitem> </listitem>
<listitem> <listitem>
<para>Zone. A logically separate section of the cluster, <para>Zone: A logically separate section of the cluster,
related to independent failure characteristics.</para> related to independent failure characteristics.</para>
</listitem> </listitem>
<listitem> <listitem>
<para>Region (optional). A logically separate section of <para>Region (optional): A logically separate section of
the cluster, representing distinct physical locations the cluster, representing distinct physical locations
such as cities or countries. Similar to zones but such as cities or countries. Similar to zones but
representing physical locations of portions of the representing physical locations of portions of the
@ -40,7 +40,7 @@
additional proxy servers.</para> additional proxy servers.</para>
<para>This document describes each storage node as a separate zone <para>This document describes each storage node as a separate zone
in the ring. At a minimum, five zones are recommended. A zone in the ring. At a minimum, five zones are recommended. A zone
is a group of nodes that is as isolated as possible from other is a group of nodes that are as isolated as possible from other
nodes (separate servers, network, power, even geography). The nodes (separate servers, network, power, even geography). The
ring guarantees that every replica is stored in a separate ring guarantees that every replica is stored in a separate
zone. This diagram shows one possible configuration for a zone. This diagram shows one possible configuration for a