From fd13de968cea54018e230b43afe5c101bfe47c49 Mon Sep 17 00:00:00 2001 From: asettle Date: Fri, 18 Sep 2015 14:46:23 +1000 Subject: [PATCH] Edits to the arch guide storage focus section 1. Removal of extra examples (prescriptive example section covers this content) 2. Grammar/spelling/general edits Change-Id: I583265a0495c446270e9f92e4f1ad29c896c427a --- .../section_architecture_storage_focus.xml | 33 ++++--------------- ...erational_considerations_storage_focus.xml | 26 +++------------ ...on_prescriptive_examples_storage_focus.xml | 11 +++---- ...tion_tech_considerations_storage_focus.xml | 1 - 4 files changed, 17 insertions(+), 54 deletions(-) diff --git a/doc/arch-design/storage_focus/section_architecture_storage_focus.xml b/doc/arch-design/storage_focus/section_architecture_storage_focus.xml index 3578e316d1..26418f1e70 100644 --- a/doc/arch-design/storage_focus/section_architecture_storage_focus.xml +++ b/doc/arch-design/storage_focus/section_architecture_storage_focus.xml @@ -82,10 +82,7 @@ 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. @@ -173,7 +170,7 @@ a list of these form factors: - Most blade servers typically support dual-socket + 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. - 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. Other factors that influence server hardware @@ -330,7 +322,7 @@ 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. @@ -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. + with the networking hardware selection and topology. Operating system and hypervisor selection affect the following areas: @@ -481,7 +471,7 @@ A storage-focused design might require the ability to use Orchestration to launch instances with Block Storage volumes to perform storage-intensive processing. - A storage-focused OpenStack design architecture typically uses the + A storage-focused OpenStack design architecture uses the following components: @@ -520,13 +510,6 @@ compute-focused architecture design. -
- Supplemental software - 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. -
-
Networking software 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. 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: + design must account for the additional resource consumption. + Some other potential design impacts include: OS-Hypervisor combination: Ensure that the diff --git a/doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml b/doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml index 0610345dfc..8838f8a69f 100644 --- a/doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml +++ b/doc/arch-design/storage_focus/section_operational_considerations_storage_focus.xml @@ -57,7 +57,7 @@ Monitoring of storage resources such as available - storage, memory and CPU. + storage, memory, and CPU. Monitoring of advanced storage performance data to @@ -90,19 +90,6 @@ -
- Management efficiency - Operations personnel are often required to replace failed - drives or nodes and provide ongoing maintenance of the storage hardware. - 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. -
-
Application awareness Well-designed applications should be aware of underlying storage @@ -122,16 +109,12 @@ Fault tolerance and availability 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. + comparing the Block Storage and Object Storage services.
Block Storage fault tolerance and availability - Block Storage resource nodes are commonly configured - with advanced RAID controllers and high performance disks to + Configure Block Storage resource nodes with advanced RAID + controllers and high performance disks to provide fault tolerance at the hardware level. 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. +
Scaling Block Storage You can upgrade Block Storage pools to add storage capacity diff --git a/doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml b/doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml index 6b00811a63..e6cee78a27 100644 --- a/doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml +++ b/doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml @@ -6,9 +6,8 @@ xml:id="prescriptive-example-storage-focus"> Prescriptive examples - Storage-focused architecture depends on - specific use cases. This section discusses three - example use cases: + Storage-focused architecture depends on specific use cases. + This section discusses three example use cases: @@ -86,9 +85,9 @@ cause performance issues. 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. + 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. 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: diff --git a/doc/arch-design/storage_focus/section_tech_considerations_storage_focus.xml b/doc/arch-design/storage_focus/section_tech_considerations_storage_focus.xml index 8dcd62fdcc..da90667da1 100644 --- a/doc/arch-design/storage_focus/section_tech_considerations_storage_focus.xml +++ b/doc/arch-design/storage_focus/section_tech_considerations_storage_focus.xml @@ -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. -