Clean up ch_hybrid.xml

Change-Id: Ie4ee2e0ba68f9323acd95a1789bf81e9d5cf667b
Implements: blueprint arch-guide

doc/arch-design/ch_hybrid.xml

@@ -5,23 +5,16 @@
   version="5.0"
   xml:id="hybrid">
     <title>Hybrid</title>
-
+    <para>A <glossterm baseform="hybrid cloud">hybrid cloud</glossterm> design
-    <para><glossterm baseform="hybrid cloud">Hybrid cloud</glossterm>,
+        is one that uses more than one cloud. For example, designs that use
-        by definition, means that the design spans
+        both an OpenStack-based private cloud and an OpenStack-based public
-        more than one cloud. An example of this kind of architecture
+        cloud, or that use an OpenStack cloud and a non-OpenStack cloud,
-        may include a situation in which the design involves more than
+        are hybrid clouds.</para>
-        one OpenStack cloud (for example, an OpenStack-based private
+    <para><glossterm baseform="bursting">Bursting</glossterm> describes the
-        cloud and an OpenStack-based public cloud), or it may be a
+        practice of creating new instances in an external cloud to alleviate
-        situation incorporating an OpenStack cloud and a non-OpenStack
+        capacity issues in a private cloud.</para>
-        cloud (for example, an OpenStack-based private cloud that
-        interacts with Amazon Web Services).
-        <glossterm baseform="bursting">Bursting</glossterm> into an external
-        cloud is the practice of creating new instances to alleviate
-        extra load where there is no available capacity in the private
-        cloud.</para>
-    <para>Some situations that could involve hybrid cloud architecture
-        include:</para>
     <itemizedlist>
+      <title>Example scenarios suited to hybrid clouds</title>
         <listitem>
             <para>Bursting from a private cloud to a public
                 cloud</para>
@@ -37,38 +30,25 @@
                 from multiple providers</para>
         </listitem>
         <listitem>
-            <para>Hybrid clouds built to support legacy systems as
+            <para>Supporting legacy systems as they transition to the
-                they transition to cloud</para>
+                cloud</para>
         </listitem>
     </itemizedlist>
-    <para>As a hybrid cloud design deals with systems that are outside
+    <para>Hybrid clouds interact with systems that are outside
-        of the control of the cloud architect or organization, a
+        the control of the private cloud administrator, and require careful
-        hybrid cloud architecture requires considering aspects of the
+        architecture to prevent conflicts with hardware, software,
-        architecture that might not have otherwise been necessary. For
+        and APIs under external control.</para>
-        example, the design may need to deal with hardware, software,
+    <para>The degree to which the architecture is OpenStack-based
-        and APIs under the control of a separate organization.</para>
+        affects your ability to accomplish tasks with native
-    <para>Similarly, the degree to which the architecture is
-        OpenStack-based will have an effect on the cloud operator or
-        cloud consumer's ability to accomplish tasks with native
         OpenStack tools. By definition, this is a situation in which
         no single cloud can provide all of the necessary
-        functionality. In order to manage the entire system, users,
+        functionality. In order to manage the entire system, we recommend
-        operators and consumers will need an overarching tool known as
+        using a cloud management platform (CMP).</para>
-        a cloud management platform (CMP). Any organization that is
+    <para>There are several commercial and open source CMPs available,
-        working with multiple clouds already has a CMP, even if that
+        but there is no single CMP that can address all needs in all scenarios,
-        CMP is the operator who logs into an external web portal and
+        and sometimes a manually-built solution is the best option.
-        launches a public cloud instance.</para>
+        This chapter includes discussion of using CMPs for managing a hybrid
-    <para>There are commercially available options, such as
+        cloud.</para>
-        Rightscale, and open source options, such as ManageIQ
-        (<link xlink:href="http://manageiq.org">http://manageiq.org</link>),
-        but there is no single CMP that can
-        address all needs in all scenarios. Whereas most of the
-        sections of this book talk about the aspects of OpenStack, an
-        architect needs to consider when designing an OpenStack
-        architecture. This section will also discuss the things the
-        architect must address when choosing or building a CMP to run
-        a hybrid cloud design, even if the CMP will be a manually
-        built solution.</para>
 
     <xi:include href="hybrid/section_user_requirements_hybrid.xml"/>
     <xi:include href="hybrid/section_tech_considerations_hybrid.xml"/>