openstack/openstack-manuals
Code Issues Proposed changes

Arch Design: Minor edits for introduction

Browse Source 
Fix typos, capitalization, add markup for a link,
uncomment para about glossary since it's not included
currently.

Change-Id: I309cf737ada1325e3fe8aa3f2e1cd5392bfade73
This commit is contained in:
Andreas Jaeger
2014-08-03 21:40:47 +02:00
parent d74779e10f
commit b58872b1be
4 changed files with 13 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -111,6 +111,8 @@
deployed.</para>
</listitem>
</itemizedlist>
<para>A Glossary covers the terms and phrases used in the
<!--
<para>A glossary covers the terms used in the
book.</para>
-->
</section>

2
doc/arch-design/introduction/section_how_this_book_was_written.xml
View File

@@ -40,7 +40,7 @@
hospitality, as well as our employers, Cisco, Cloudscaling,
Comcast, EMC, Mirantis, Rackspace, Red Hat, Verizon, and
VMware, for enabling us to contribute our time. We would
especially like to think Anne Gentle and Kenneth Hui for all
especially like to thank Anne Gentle and Kenneth Hui for all
of their shepherding and organization in making this
happen.</para>
<para>The author team includes:</para>

6
doc/arch-design/introduction/section_intended_audience.xml
View File

@@ -8,8 +8,10 @@
<para>This book has been written for architects and designers of
OpenStack clouds. This book is not intended for people who are
deploying OpenStack. For a guide on deploying and operating
OpenStack, please refer to the Operations Guide
http://docs.openstack.org/openstack-ops.</para>
OpenStack, please refer to the <citetitle>OpenStack Operations
Guide</citetitle> (<link
xlink:href="http://docs.openstack.org/openstack-ops">http://docs.openstack.org/openstack-ops</link>).
</para>
<para>The reader should have prior knowledge of cloud architecture
and principles, experience in enterprise system design, Linux
and virtualization experience, and a basic understanding of

13
doc/arch-design/introduction/section_methodology.xml
View File

@@ -195,14 +195,11 @@
<term>Durability and resilience</term>
<listitem>
<para>
Despite the existence of SLAs, the one reality of
the cloud is that Things Break. Servers go down,
network connections are disrupted, other tenants
on a server ramp up the load to make the server
unusable. Any number of things can happen, and an
application that isn't built to withstand this
kind of disruption isn't going to work
properly.
Despite the existence of SLAs, things break:
servers go down, network connections are
disrupted, or too many tenants on a server make a
server unusable. An application must be sturdy
enough to contend with these issues.
</para>
</listitem>
</varlistentry>