storage focused -> storage-focused

Use storage-focused cloud.

Also, remove one extra 'and'.

Change-Id: I539938f378c0be410a25b3d8508146727b0b16aa
This commit is contained in:
Andreas Jaeger
2015-03-11 21:20:49 +01:00
parent 2997f8a7f0
commit 09e4ffeeae

View File

@@ -7,7 +7,7 @@
<?dbhtml stop-chunking?>
<title>Technical considerations</title>
<para>Some of the key technical considerations that are critical
to a storage focused OpenStack design architecture
to a storage-focused OpenStack design architecture
include:</para>
<variablelist>
<varlistentry>
@@ -31,10 +31,10 @@
<varlistentry>
<term>Scale</term>
<listitem>
<para>Scaling storage solutions in a storage focused
<para>Scaling storage solutions in a storage-focused
OpenStack architecture design is driven by initial
requirements, including <glossterm>IOPS</glossterm>,
capacity, and bandwidth, and future needs. Planning
capacity, bandwidth, and future needs. Planning
capacity based on projected needs over the
course of a budget cycle is important for a design.
The architecture should balance cost
@@ -72,7 +72,7 @@
<listitem>
<para>You must address a range of storage
management-related considerations in
the design of a storage focused OpenStack cloud. These
the design of a storage-focused OpenStack cloud. These
considerations include, but are not limited to, backup
strategy (and restore strategy, since a backup that
can not be restored is useless), data
@@ -92,7 +92,7 @@
</listitem>
</varlistentry>
</variablelist>
<para>When building a storage focused OpenStack architecture,
<para>When building a storage-focused OpenStack architecture,
strive to build a flexible design based on an
industry standard core. One way of accomplishing this might be
through the use of different back ends serving different use