<?xml version="1.0" encoding="UTF-8"?> <section xml:id="example-object-storage-installation-architecture" xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"> <title>Example Object Storage installation architecture</title> <itemizedlist> <listitem> <para>node. A host machine that runs one or more OpenStack Object Storage services.</para> </listitem> <listitem> <para>Proxy node. Runs Proxy services.</para> </listitem> <listitem> <para>Storage node. Runs Account, Container, and Object services.</para> </listitem> <listitem> <para>Ring. A set of mappings between OpenStack Object Storage data to physical devices.</para> </listitem> <listitem> <para>Replica. A copy of an object. By default, three copies are maintained in the cluster.</para> </listitem> <listitem> <para>Zone. A logically separate section of the cluster, related to independent failure characteristics.</para> </listitem> </itemizedlist> <para>To increase reliability and performance, you can add additional proxy servers.</para> <para>This document describes each storage node as a separate 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 nodes (separate servers, network, power, even geography). The ring guarantees that every replica is stored in a separate zone. This diagram shows one possible configuration for a minimal installation:</para> <!-- we need to fix this diagram - the auth node isn't a thing anymore--> <para><inlinemediaobject> <imageobject> <imagedata fileref="../figures/swift_install_arch.png" /> </imageobject> </inlinemediaobject></para> </section>