Clean up of section_prescriptive_examples_storage_focus.xml
Minor edits to the prescriptive examples section of the storage focused chapter Change-Id: I20cb3298638ce7a731a3a3fea39bba5c44d73a34 Implements: blueprint arch-guide
This commit is contained in:
parent
90f73d08b6
commit
2db522feb7
@ -6,9 +6,9 @@
|
||||
xml:id="prescriptive-example-storage-focus">
|
||||
<?dbhtml stop-chunking?>
|
||||
<title>Prescriptive examples</title>
|
||||
<para>Storage-focused architecture highly depends on the
|
||||
specific use case. This section discusses three
|
||||
specific example use cases:</para>
|
||||
<para>Storage-focused architecture depends on
|
||||
specific use cases. This section discusses three
|
||||
example use cases:</para>
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
@ -38,9 +38,9 @@
|
||||
</imageobject>
|
||||
</mediaobject>
|
||||
</para>
|
||||
<para>The example REST interface, presented as a traditional Object store running
|
||||
on traditional spindles, does not require a high performance
|
||||
caching tier.</para>
|
||||
<para>The example REST interface, presented as a traditional Object
|
||||
store running on traditional spindles, does not require a high
|
||||
performance caching tier.</para>
|
||||
<para>This example uses the following components:</para>
|
||||
<para>Network:</para>
|
||||
<itemizedlist>
|
||||
@ -80,18 +80,18 @@
|
||||
|
||||
<section xml:id="compute-analytics-with-sahara">
|
||||
<title>Compute analytics with Data processing service</title>
|
||||
<para>Analytics of large data sets are highly dependent on the performance
|
||||
<para>Analytics of large data sets are dependent on the performance
|
||||
of the storage system. Clouds using storage systems such as
|
||||
Hadoop Distributed File System (HDFS) have inefficiencies which can
|
||||
cause performance issues.
|
||||
</para>
|
||||
<para>One potential solution to this problem is the implementation of storage
|
||||
systems designed for performance. Parallel file systems have previously
|
||||
filled this need in the HPC space and are suitable
|
||||
for large scale performance-orientated systems.</para>
|
||||
<para>One potential solution to this problem is the implementation of
|
||||
storage systems designed for performance. Parallel file systems have
|
||||
previously filled this need in the HPC space and are suitable for large
|
||||
scale performance-orientated systems.</para>
|
||||
<para>OpenStack has integration with Hadoop to manage the Hadoop cluster
|
||||
within the cloud. This diagram shows an OpenStack store with a high
|
||||
performance requirement:
|
||||
within the cloud. The following diagram shows an OpenStack store with
|
||||
a high performance requirement:
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata contentwidth="4in"
|
||||
@ -123,8 +123,9 @@
|
||||
or Gluster.</para>
|
||||
<para>This system can provide additional performance. For example,
|
||||
in the database example below, a portion of the SSD pool can act
|
||||
as a block device to the Database server. In the high performance analytics
|
||||
example, the inline SSD cache layer accelerates the REST interface.</para>
|
||||
as a block device to the Database server. In the high performance
|
||||
analytics example, the inline SSD cache layer accelerates the REST
|
||||
interface.</para>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata contentwidth="4in"
|
||||
@ -182,7 +183,7 @@
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
<para>Using an SSD cache layer, you can present block devices
|
||||
directly to Hypervisors or instances. The REST interface can
|
||||
directly to hypervisors or instances. The REST interface can
|
||||
also use the SSD cache systems as an inline cache.
|
||||
</para>
|
||||
</section>
|
||||
|
Loading…
Reference in New Issue
Block a user