openstack/openstack-manuals
Code Issues Proposed changes

Clean up ch_hybrid.xml

Browse Source 
Change-Id: Ie4ee2e0ba68f9323acd95a1789bf81e9d5cf667b
Implements: blueprint arch-guide
This commit is contained in:
Brian Moss 2015-08-13 14:16:49 +10:00
parent 79d32c6607
commit ff1353d215
1 changed files with 24 additions and 44 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

68
doc/arch-design/ch_hybrid.xml
View File

@ -5,23 +5,16 @@
version="5.0"
xml:id="hybrid">
<title>Hybrid</title>
<para><glossterm baseform="hybrid cloud">Hybrid cloud</glossterm>,
by definition, means that the design spans
more than one cloud. An example of this kind of architecture
may include a situation in which the design involves more than
one OpenStack cloud (for example, an OpenStack-based private
cloud and an OpenStack-based public cloud), or it may be a
situation incorporating an OpenStack cloud and a non-OpenStack
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>
<para>A <glossterm baseform="hybrid cloud">hybrid cloud</glossterm> design
is one that uses more than one cloud. For example, designs that use
both an OpenStack-based private cloud and an OpenStack-based public
cloud, or that use an OpenStack cloud and a non-OpenStack cloud,
are hybrid clouds.</para>
<para><glossterm baseform="bursting">Bursting</glossterm> describes the
practice of creating new instances in an external cloud to alleviate
capacity issues in a private cloud.</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
they transition to cloud</para>
<para>Supporting legacy systems as they transition to the
cloud</para>
</listitem>
</itemizedlist>
<para>As a hybrid cloud design deals with systems that are outside
of the control of the cloud architect or organization, a
hybrid cloud architecture requires considering aspects of the
architecture that might not have otherwise been necessary. For
example, the design may need to deal with hardware, software,
and APIs under the control of a separate organization.</para>
<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
<para>Hybrid clouds interact with systems that are outside
the control of the private cloud administrator, and require careful
architecture to prevent conflicts with hardware, software,
and APIs under external control.</para>
<para>The degree to which the architecture is OpenStack-based
affects your 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,
operators and consumers will need an overarching tool known as
a cloud management platform (CMP). Any organization that is
working with multiple clouds already has a CMP, even if that
CMP is the operator who logs into an external web portal and
launches a public cloud instance.</para>
<para>There are commercially available options, such as
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>
functionality. In order to manage the entire system, we recommend
using a cloud management platform (CMP).</para>
<para>There are several commercial and open source CMPs available,
but there is no single CMP that can address all needs in all scenarios,
and sometimes a manually-built solution is the best option.
This chapter includes discussion of using CMPs for managing a hybrid
cloud.</para>
<xi:include href="hybrid/section_user_requirements_hybrid.xml"/>
<xi:include href="hybrid/section_tech_considerations_hybrid.xml"/>