60 lines
2.7 KiB
XML
60 lines
2.7 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<chapter xmlns="http://docbook.org/ns/docbook"
|
|
xmlns:xi="http://www.w3.org/2001/XInclude"
|
|
xmlns:xlink="http://www.w3.org/1999/xlink"
|
|
version="5.0"
|
|
xml:id="hybrid">
|
|
<title>Hybrid</title>
|
|
<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>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Disaster recovery</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Development and testing</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Federated cloud, enabling users to choose resources
|
|
from multiple providers</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Supporting legacy systems as they transition to the
|
|
cloud</para>
|
|
</listitem>
|
|
</itemizedlist>
|
|
<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, 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"/>
|
|
<xi:include href="hybrid/section_operational_considerations_hybrid.xml"/>
|
|
<xi:include href="hybrid/section_architecture_hybrid.xml"/>
|
|
<xi:include href="hybrid/section_prescriptive_examples_hybrid.xml"/>
|
|
|
|
</chapter>
|