b2235bf3fb
Execluded all XML files in the directory doc/common/tables because they are autogenerated. The XML root element of Docbook XML files should match the following format: <ELEMENT 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" xml:id="THE_XML_ID_OF_THE_ELEMENT"> Change-Id: If12091be81ec8b2e6e53bfcb4c3a883a65e24736
126 lines
4.7 KiB
XML
126 lines
4.7 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<section 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"
|
|
xml:id="section_objectstorage_features">
|
|
<title>Features and benefits</title>
|
|
|
|
<informaltable>
|
|
<thead>
|
|
<tr>
|
|
<th>Features</th>
|
|
<th>Benefits</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody>
|
|
<tr>
|
|
<td><emphasis role="bold">Leverages commodity hardware</emphasis></td>
|
|
<td>No lock-in, lower price/GB.</td>
|
|
</tr>
|
|
<tr>
|
|
<td><emphasis role="bold">HDD/node failure agnostic</emphasis></td>
|
|
<td>Self-healing, reliable, data redundancy protects from
|
|
failures.</td>
|
|
</tr>
|
|
<tr>
|
|
<td><emphasis role="bold">Unlimited storage</emphasis></td>
|
|
<td>Large and flat namespace, highly scalable read/write
|
|
access, able to serve content directly from storage system.</td>
|
|
</tr>
|
|
<tr>
|
|
<td><emphasis role="bold">Multi-dimensional scalability</emphasis>
|
|
</td>
|
|
<td>Scale-out architecture: Scale vertically and
|
|
horizontally-distributed storage. Backs up and archives
|
|
large amounts of data with linear performance.</td>
|
|
</tr>
|
|
<tr>
|
|
<td><emphasis role="bold">Account/container/object structure</emphasis></td>
|
|
<td>No nesting, not a traditional file system: Optimized
|
|
for scale, it scales to multiple petabytes and billions of
|
|
objects.</td>
|
|
</tr>
|
|
<tr>
|
|
<td><emphasis role="bold">Built-in replication 3✕ +
|
|
data redundancy (compared with 2✕ on RAID)</emphasis>
|
|
</td>
|
|
<td>A configurable number of accounts, containers and
|
|
object copies for high availability.</td>
|
|
</tr>
|
|
<tr>
|
|
<td><emphasis role="bold">Easily add capacity (unlike
|
|
RAID resize)</emphasis></td>
|
|
<td>Elastic data scaling with ease</td>
|
|
</tr>
|
|
<tr>
|
|
<td><emphasis role="bold">No central database</emphasis></td>
|
|
<td>Higher performance, no bottlenecks</td>
|
|
</tr>
|
|
<tr>
|
|
<td><emphasis role="bold">RAID not required</emphasis></td>
|
|
<td>Handle many small, random reads and writes efficiently</td>
|
|
</tr>
|
|
<tr>
|
|
<td><emphasis role="bold">Built-in management utilities</emphasis></td>
|
|
<td>Account management: Create, add, verify, and delete
|
|
users; Container management: Upload, download, and verify;
|
|
Monitoring: Capacity, host, network, log trawling, and
|
|
cluster health.</td>
|
|
</tr>
|
|
<tr>
|
|
<td><emphasis role="bold">Drive auditing</emphasis></td>
|
|
<td>Detect drive failures preempting data corruption</td>
|
|
</tr>
|
|
<tr>
|
|
<td><emphasis role="bold">Expiring objects</emphasis></td>
|
|
<td>Users can set an expiration time or a TTL on an object
|
|
to control access</td>
|
|
</tr>
|
|
<tr>
|
|
<td><emphasis role="bold">Direct object access</emphasis></td>
|
|
<td>Enable direct browser access to content, such as for
|
|
a control panel</td>
|
|
</tr>
|
|
<tr>
|
|
<td><emphasis role="bold">Realtime visibility into client
|
|
requests</emphasis></td>
|
|
<td>Know what users are requesting.</td>
|
|
</tr>
|
|
<tr>
|
|
<td><emphasis role="bold">Supports S3 API</emphasis></td>
|
|
<td>Utilize tools that were designed for the popular S3
|
|
API.</td>
|
|
</tr>
|
|
<tr>
|
|
<td><emphasis role="bold">Restrict containers per
|
|
account</emphasis></td>
|
|
<td>Limit access to control usage by user.</td>
|
|
</tr>
|
|
<tr>
|
|
<td><emphasis role="bold">Support for NetApp, Nexenta,
|
|
SolidFire</emphasis></td>
|
|
<td>Unified support for block volumes using a variety of
|
|
storage systems.</td>
|
|
</tr>
|
|
<tr>
|
|
<td><emphasis role="bold">Snapshot and backup API for
|
|
block volumes</emphasis></td>
|
|
<td>Data protection and recovery for VM data.</td>
|
|
</tr>
|
|
<tr>
|
|
<td><emphasis role="bold">Standalone volume API
|
|
available</emphasis></td>
|
|
<td>Separate endpoint and API for integration with other
|
|
compute systems.</td>
|
|
</tr>
|
|
<tr>
|
|
<td><emphasis role="bold">Integration with
|
|
Compute</emphasis></td>
|
|
<td>Fully integrated with Compute for attaching block
|
|
volumes and reporting on usage.</td>
|
|
</tr>
|
|
</tbody>
|
|
</informaltable>
|
|
</section>
|