openstack/openstack-manuals
Code Issues Proposed changes

Edits to the arch guide storage focus section

Browse Source 
1. Removal of extra examples (prescriptive example
   section covers this content)
2. Grammar/spelling/general edits

Change-Id: I583265a0495c446270e9f92e4f1ad29c896c427a
This commit is contained in:
asettle 2015-09-18 14:46:23 +10:00
parent e69bb461af
commit fd13de968c
4 changed files with 17 additions and 54 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

33
doc/arch-design/storage_focus/section_architecture_storage_focus.xml
View File

@ -82,10 +82,7 @@
<listitem>
<para>Based on the selected storage solution, ensure the
connectivity matches the storage solution requirements.
For example, if you select a centralized storage array,
determine how the hypervisors connect to the storage
array. Connectivity can affect latency and thus
performance. We recommended confirming that the network
We recommended confirming that the network
characteristics minimize latency to boost the
overall performance of the design.</para>
</listitem>
@ -173,7 +170,7 @@
a list of these form factors:</para>
<itemizedlist>
<listitem>
<para>Most blade servers typically support dual-socket
<para>Most blade servers support dual-socket
multi-core CPUs. Choose either full width or full height
blades to avoid the limit. High density blade servers
support up to 16 servers in only 10
@ -222,11 +219,6 @@
that support multiple independent servers in a single
2U or 3U enclosure, "sled servers", deliver increased
density as compared to a typical 1U-2U rack-mounted servers.</para>
<para>For example, many sled servers offer four independent
dual-socket nodes in 2U for a total of 8 CPU sockets
in 2U. However, the dual-socket limitation on
individual nodes may not be sufficient to offset their
additional cost and configuration complexity.</para>
</listitem>
</itemizedlist>
<para>Other factors that influence server hardware
@ -330,7 +322,7 @@
<listitem>
<para>Ensure that the physical data
center provides the necessary power for the selected
network hardware. This is not typically an issue for
network hardware. This is not an issue for
top of rack (ToR) switches, but may be an issue for
spine switches in a leaf and spine fabric, or end of
row (EoR) switches.</para>
@ -374,9 +366,7 @@
on the overall design and also affect server hardware
selection. Ensure the selected operating system and
hypervisor combination support the storage hardware and work
with the networking hardware selection and topology.
For example, Link Aggregation Control Protocol (LACP) requires
support from both the operating system and hypervisor.</para>
with the networking hardware selection and topology.</para>
<para>Operating system and hypervisor selection affect the following
areas:</para>
<variablelist>
@ -481,7 +471,7 @@
<para>A storage-focused design might require the ability to use
Orchestration to launch instances with Block Storage volumes to
perform storage-intensive processing.</para>
<para>A storage-focused OpenStack design architecture typically uses the
<para>A storage-focused OpenStack design architecture uses the
following components:</para>
<itemizedlist>
<listitem>
@ -520,13 +510,6 @@
compute-focused architecture design.</para>
</section>
<section xml:id="supplemental-software-arch-storage">
<title>Supplemental software</title>
<para>While OpenStack is a fairly complete collection of software
projects for building a platform for cloud services, you may need
to add other pieces of software.</para>
</section>
<section xml:id="networking-software-arch-storage">
<title>Networking software</title>
<para>OpenStack Networking (neutron) provides a wide variety of networking
@ -591,10 +574,8 @@
both alert and automatically attempt to remediate some of the
more commonly known issues.</para>
<para>If you require any of these software packages, the
design must account for the additional resource consumption
(CPU, RAM, storage, and network bandwidth for a log
aggregation solution, for example). Some other potential
design impacts include:</para>
design must account for the additional resource consumption.
Some other potential design impacts include:</para>
<itemizedlist>
<listitem>
<para>OS-Hypervisor combination: Ensure that the

26
doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml
View File

@ -57,7 +57,7 @@
</listitem>
<listitem>
<para>Monitoring of storage resources such as available
storage, memory and CPU.</para>
storage, memory, and CPU.</para>
</listitem>
<listitem>
<para>Monitoring of advanced storage performance data to
@ -90,19 +90,6 @@
</listitem>
</itemizedlist>
<section xml:id="management-efficiency">
<title>Management efficiency</title>
<para>Operations personnel are often required to replace failed
drives or nodes and provide ongoing maintenance of the storage hardware.</para>
<para>Provisioning and configuration of new or upgraded storage is
another important consideration when it comes to management of
resources. The ability to easily deploy, configure, and manage
storage hardware results in a solution that is easy to
manage. This also makes use of management systems that can
automate other pieces of the overall solution. For example,
replication, retention, data backup and recovery.</para>
</section>
<section xml:id="application-awareness">
<title>Application awareness</title>
<para>Well-designed applications should be aware of underlying storage
@ -122,16 +109,12 @@
<title>Fault tolerance and availability</title>
<para>Designing for fault tolerance and availability of storage
systems in an OpenStack cloud is vastly different when
comparing the Block Storage and Object Storage services. The
Object Storage service design features consistency and
partition tolerance as a function of the application.
Therefore, it does not have any reliance on hardware RAID
controllers to provide redundancy for physical disks.</para>
comparing the Block Storage and Object Storage services.</para>
<section xml:id="block-storage-fault-tolerance-and-availability">
<title>Block Storage fault tolerance and availability</title>
<para>Block Storage resource nodes are commonly configured
with advanced RAID controllers and high performance disks to
<para>Configure Block Storage resource nodes with advanced RAID
controllers and high performance disks to
provide fault tolerance at the hardware level.</para>
<para>Deploy high performing storage solutions
such as SSD disk drives or flash storage systems for applications
@ -257,6 +240,7 @@
process, adding capacity and bandwidth to the Object Storage
systems is a complex task that requires careful planning and
consideration during the design phase.</para>
<section xml:id="scaling-block-storage">
<title>Scaling Block Storage</title>
<para>You can upgrade Block Storage pools to add storage capacity

11
doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml
View File

@ -6,9 +6,8 @@
xml:id="prescriptive-example-storage-focus">
<?dbhtml stop-chunking?>
<title>Prescriptive examples</title>
<para>Storage-focused architecture depends on
specific use cases. This section discusses three
example use cases:</para>
<para>Storage-focused architecture depends on specific use cases.
This section discusses three example use cases:</para>
<itemizedlist>
<listitem>
<para>
@ -86,9 +85,9 @@
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>
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. The following diagram shows an OpenStack store with
a high performance requirement:

1
doc/arch-design/storage_focus/section_tech_considerations_storage_focus.xml
View File

@ -97,5 +97,4 @@
industry standard core. One way of accomplishing this might be
through the use of different back ends serving different use
cases.</para>
<!--I feel like this last para just 'ends'. Is there more information to be put here? A.S -->
</section>