<?xml version="1.0" encoding="UTF-8"?>
<section xml:id="object-storage-system-requirements"
    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">
    <?dbhtml-stop-chunking?>
    <title>System requirements</title>
    <para><emphasis role="bold">Hardware</emphasis>: OpenStack Object
        Storage is designed to run on commodity hardware.</para>
    <note>
        <para>When you install only the Object Storage and Identity
            Service, you cannot use the dashboard unless you also
            install Compute and the Image Service.</para>
    </note>
    <table rules="all">
        <caption>Hardware recommendations</caption>
        <col width="20%"/>
        <col width="23%"/>
        <col width="57%"/>

        <thead>
            <tr>
                <td>Server</td>
                <td>Recommended Hardware</td>
                <td>Notes</td>
            </tr>
        </thead>
        <tbody>
            <tr>
                <td><para>Object Storage object servers</para></td>
                <td>
                    <para>Processor: dual quad
                        core</para><para>Memory: 8 or 12 GB RAM</para>
                    <para>Disk space: optimized for cost per GB</para>
                    <para>Network: one 1 GB Network Interface Card
                        (NIC)</para></td>
                <td><para>The amount of disk space depends on how much
                        you can fit into the rack efficiently. You
                        want to optimize these for best cost per GB
                        while still getting industry-standard failure
                        rates. At Rackspace, our storage servers are
                        currently running fairly generic 4U servers
                        with 24 2T SATA drives and 8 cores of
                        processing power. RAID on the storage drives
                        is not required and not recommended. Swift's
                        disk usage pattern is the worst case possible
                        for RAID, and performance degrades very
                        quickly using RAID 5 or 6.</para>
                    <para>As an example, Rackspace runs Cloud Files
                        storage servers with 24 2T SATA drives and 8
                        cores of processing power. Most services
                        support either a worker or concurrency value
                        in the settings. This allows the services to
                        make effective use of the cores
                        available.</para></td>
            </tr>
            <tr>
                <td><para>Object Storage container/account
                        servers</para></td>
                <td>
                    <para>Processor: dual quad core</para>
                    <para>Memory: 8 or 12 GB RAM</para>
                    <para>Network: one 1 GB Network Interface Card
                        (NIC)</para></td>
                <td><para>Optimized for IOPS due to tracking with
                        SQLite databases.</para></td>
            </tr>
            <tr>
                <td><para>Object Storage proxy server</para></td>
                <td>
                    <para>Processor: dual quad
                        core</para><para>Network: one 1 GB Network
                        Interface Card (NIC)</para></td>
                <td><para>Higher network throughput offers better
                        performance for supporting many API
                        requests.</para>
                    <para>Optimize your proxy servers for best CPU
                        performance. The Proxy Services are more CPU
                        and network I/O intensive. If you are using 10
                        GB networking to the proxy, or are terminating
                        SSL traffic at the proxy, greater CPU power is
                        required.</para></td>
            </tr>
        </tbody>
    </table>
    <para><emphasis role="bold">Operating system</emphasis>: OpenStack
        Object Storage currently runs on Ubuntu, RHEL, CentOS, Fedora,
        openSUSE, or SLES.</para>
    <para><emphasis role="bold">Networking</emphasis>: 1Gpbs or 10
        Gbps is suggested internally. For OpenStack Object Storage, an
        external network should connect the outside world to the proxy
        servers, and the storage network is intended to be isolated on
        a private network or multiple private networks.</para>
    <para><emphasis role="bold">Database</emphasis>: For OpenStack
        Object Storage, a SQLite database is part of the OpenStack
        Object Storage container and account management
        process.</para>
    <para><emphasis role="bold">Permissions</emphasis>: You can
        install OpenStack Object Storage either as root or as a user
        with sudo permissions if you configure the sudoers file to
        enable all the permissions.</para>
</section>