Merge "Removed unnecessary text"
This commit is contained in:
commit
47f1cadeac
@ -5,26 +5,10 @@
|
||||
version="5.0"
|
||||
xml:id="arch-guide-why-and-who-we-wrote-this-book">
|
||||
<title>Why and how we wrote this book</title>
|
||||
<para>The velocity at which OpenStack environments are moving from
|
||||
proof-of-concepts to production deployments is leading to
|
||||
increasing questions and issues related to architecture design
|
||||
considerations. By and large these considerations are not
|
||||
addressed in the existing documentation, which typically
|
||||
focuses on the specifics of deployment and configuration
|
||||
options or operational considerations, rather than the bigger
|
||||
picture.</para>
|
||||
<para>We wrote this book to guide readers in designing an
|
||||
OpenStack architecture that meets the needs of their
|
||||
organization. This guide concentrates on identifying important
|
||||
design considerations for common cloud use cases and provides
|
||||
examples based on these design guidelines. This guide does not
|
||||
aim to provide explicit instructions for installing and
|
||||
configuring the cloud, but rather focuses on design principles
|
||||
as they relate to user requirements as well as technical and
|
||||
operational considerations. For specific guidance with
|
||||
installation and configuration there are a number of resources
|
||||
already available in the OpenStack documentation that help in
|
||||
that area.</para>
|
||||
<para>We wrote this book to guide you in designing an OpenStack cloud
|
||||
architecture that meets the needs of your organization. This guide
|
||||
identifies important design considerations for common cloud use cases
|
||||
and provides examples.</para>
|
||||
<para>This book was written in a book sprint format, which is a
|
||||
facilitated, rapid development production method for books.
|
||||
For more information, see the Book Sprints website
|
||||
|
Loading…
x
Reference in New Issue
Block a user