Edited Intro Chapter
Edited for clarity. Change-Id: I276379682217d66edc66ff73de458961ea2981ed Implements: blueprint arch-guide
This commit is contained in:
parent
79d32c6607
commit
f629178ae5
@ -6,30 +6,11 @@
|
||||
xml:id="introduction">
|
||||
<title>Introduction</title>
|
||||
|
||||
<para>OpenStack is a leader in the cloud technology gold rush, as
|
||||
organizations of all stripes discover the increased
|
||||
flexibility and speed to market that self-service cloud and
|
||||
Infrastructure-as-a-Service (IaaS) provides. However, in order
|
||||
to reap those benefits, the cloud must be designed and
|
||||
architected properly.</para>
|
||||
<para>A well-architected cloud provides a stable IT environment
|
||||
that offers easy access to needed resources, usage-based
|
||||
expenses, extra capacity on demand, disaster recovery, and a
|
||||
secure environment. A well-architected cloud does not
|
||||
magically build itself. It requires careful consideration of a
|
||||
multitude of factors both technical and non-technical.</para>
|
||||
<para>There is no single architecture that is "right" for an
|
||||
OpenStack cloud deployment. OpenStack can be used for any
|
||||
number of different purposes, each with its own
|
||||
particular requirements and architectural
|
||||
peculiarities.</para>
|
||||
<para>This book is designed to examine some of the most common
|
||||
uses for OpenStack clouds (and some less common uses)
|
||||
and to provide knowledge and advice to help explain the
|
||||
issues that require consideration. These examples, coupled
|
||||
with a wealth of knowledge and advice will help an organization
|
||||
design and build a well-architected OpenStack cloud to fit its unique
|
||||
requirements.</para>
|
||||
<para><glossterm>OpenStack</glossterm> is a fully-featured, self-service
|
||||
cloud. Consider the design of your cloud carefully so that it will
|
||||
accurately suit your needs.</para>
|
||||
<para>This book examines some of the most common uses for OpenStack clouds, and
|
||||
explains the considerations for each use case.</para>
|
||||
|
||||
<xi:include href="introduction/section_intended_audience.xml"/>
|
||||
<xi:include href="introduction/section_how_this_book_is_organized.xml"/>
|
||||
|
Loading…
Reference in New Issue
Block a user