[archguide-mitaka-reorg]Introduction: How book is organized

Change-Id: Id4497b5f26182804260c536f95dfbee392196452
Implements: blueprint archguide-mitaka-reorg

doc/arch-design-draft/source/introduction.rst

@@ -23,3 +23,41 @@ Before reading this book, we recommend:
 * Experience in enterprise system design.
 * Linux and virtualization experience.
 * A basic understanding of networking principles and protocols.
+
+How this book is organized
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+This book follows a structure similar to what system architects would use in
+developing cloud architecture design documents. The sections covered are:
+
+*  :doc:`Identifying stakeholders<identifying-stakeholders>`: Discover
+   different business requirements and architecture design based on different
+   internal and external stakeholders.
+
+*  :doc:`Functional requirements<functional-requirements>`: Information for
+   SMEs on deployment methods and how they will affect deployment cost.
+
+*  :doc:`User requirements<user-requirements>`: Information for SMEs on
+   business and technical requirements.
+
+*  :doc:`Operator requirements<operator-requirements>`: Information on
+   :term:`Service Level Agreement (SLA)` considerations, selecting the right
+   hardware for servers and switches, and integration with external
+   :term:`identity provider`.
+
+*  :doc:`Capacity planning and scaling<capacity-planning-scaling>`: Information
+   on storage and networking.
+
+*  :doc:`High Availability<high-availability>`: Separation of data plane and
+   control plane, and how to eliminate single ponits of failure.
+
+*  :doc:`Security requirements<security-requirements>`: The security
+   requirements you will need to consider for the different OpenStack
+   scenarios.
+
+*  :doc:`Legal requirements<legal-requirements>`: The legal requirements you
+   will need to consider for the different OpenStack scenarios.
+
+*  :doc:`Example architectures<example-architectures>`: An examination of some
+   of the most common uses for OpenStack clouds, and explanations of the
+   considerations for each use case.

doc/glossary/glossary-terms.xml

@@ -8163,6 +8163,18 @@
       </glossdef>
     </glossentry>
 
+    <glossentry>
+        <glossterm>Service Level Agreement (SLA)</glossterm>
+      <indexterm class="singular">
+          <primary>Service Level Agreement (SLA)</primary>
+        </indexterm>
+
+        <glossdef>
+            <para>Contractual obligations that ensure the availability of a
+              service.</para>
+        </glossdef>
+    </glossentry>
+
     <glossentry>
       <glossterm>SmokeStack</glossterm>
       <indexterm class="singular">