openstack/openstack-manuals
Code Issues Proposed changes

Edited How this book is organized.

Browse Source 
1. Removed unnecessary text.
2. Commented out how each chapter is organized with
   explanation.

Change-Id: I2b88e515fab7fbe910404714c59148866e9cc145
Implements: blueprint arch-guide
This commit is contained in:
Deena 2015-08-13 13:35:51 +10:00 committed by asettle
parent 17a609fc2e
commit 9b11103745
1 changed files with 26 additions and 39 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

65
doc/arch-design/introduction/section_how_this_book_is_organized.xml
View File

@ -5,63 +5,48 @@
version="5.0"
xml:id="arch-guide-how-this-book-is-organized">
<title>How this book is organized</title>
<para>This book has been organized into various chapters that help
define the use cases associated with making architectural
choices related to an <glossterm>OpenStack</glossterm> cloud
installation. Each
chapter is intended to stand alone to encourage individual
chapter readability, however each chapter is designed to
contain useful information that may be applicable in
situations covered by other chapters. Cloud architects may use
this book as a comprehensive guide by reading all of the use
cases, but it is also possible to review only the chapters
which pertain to a specific use case. When choosing to read
specific use cases, note that it may be necessary to read more
than one section of the guide to formulate a complete design
for the cloud. The use cases covered in this guide
include:</para>
<para>This book examines some of the most common uses for OpenStack
clouds, and explains the considerations for each use case.
Cloud architects may use this book as a comprehensive guide by
reading all of the use cases, but it is also possible to review
only the chapters which pertain to a specific use case.
The use cases covered in this guide include:</para>
<itemizedlist>
<listitem>
<para>
<link linkend="generalpurpose">General purpose</link>: A
cloud built with common components that should address
<link linkend="generalpurpose">General purpose</link>: Uses common components that address
80% of common use cases.
</para>
</listitem>
<listitem>
<para>
<link linkend="compute_focus">Compute focused</link>: A
cloud designed to address compute intensive workloads
<link linkend="compute_focus">Compute focused</link>: For compute intensive workloads
such as high performance computing (HPC).
</para>
</listitem>
<listitem>
<para>
<link linkend="storage_focus">Storage focused</link>: A
cloud focused on storage intensive workloads such as
<link linkend="storage_focus">Storage focused</link>: For storage intensive workloads such as
data analytics with parallel file systems.
</para>
</listitem>
<listitem>
<para>
<link linkend="network_focus">Network focused</link>: A
cloud depending on high performance and reliable
<link linkend="network_focus">Network focused</link>: For high performance and reliable
networking, such as a <glossterm
>content delivery network (CDN)</glossterm>.
</para>
</listitem>
<listitem>
<para>
<link linkend="multi_site">Multi-site</link>: A cloud
built with multiple sites available for application
<link linkend="multi_site">Multi-site</link>: For applications that require multiple site
deployments for geographical, reliability or data
locality reasons.
</para>
</listitem>
<listitem>
<para>
<link linkend="hybrid">Hybrid cloud</link>: An
architecture where multiple disparate clouds are
<link linkend="hybrid">Hybrid cloud</link>: Uses multiple disparate clouds
connected either for failover, hybrid cloud bursting, or
availability.
</para>
@ -69,17 +54,22 @@
<listitem>
<para>
<link linkend="massively_scalable">Massively
scalable</link>: An architecture that is intended for
cloud service providers or other extremely large
installations.
scalable</link>: For
cloud service providers or other large
installations
</para>
</listitem>
<listitem>
<para>
<link linkend="specialized">Specialized cases</link>: Architectures that have not
previously been covered in the defined use cases.
</para>
</listitem>
</itemizedlist>
<para>
A chapter titled <link linkend="specialized">Specialized
cases</link> provides information on architectures that have not
previously been covered in the defined use cases.
</para>
<!-- This section is currrently commented out as it is irrelevant within the current
context. However, there are plans to use this list in the future. Please do not remove.
<para>Each chapter in the guide is then further broken down into
the following sections:</para>
<itemizedlist>
@ -112,8 +102,5 @@
deployed.</para>
</listitem>
</itemizedlist>
<para>
A glossary covers the terms used in the book.
</para>
-->
</section>