
Move the introductory sections one level up, removing the separate section for them. This reads much nicer in HTML now. There's also no need to name the first paragraphs of a chapter "Introduction", this is implied. Change-Id: Ife4275807561dae2ca57dc71b7602240efa94663
42 lines
1.8 KiB
XML
42 lines
1.8 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="multi_site">
|
|
<title>Multi-site</title>
|
|
|
|
<para>A multi-site OpenStack environment is one in which services
|
|
located in more than one data center are used to provide the
|
|
overall solution. Usage requirements of different multi-site
|
|
clouds may vary widely, however they share some common needs.
|
|
OpenStack is capable of running in a multi-region
|
|
configuration allowing some parts of OpenStack to effectively
|
|
manage a grouping of sites as a single cloud. With some
|
|
careful planning in the design phase, OpenStack can act as an
|
|
excellent multi-site cloud solution for a multitude of
|
|
needs.</para>
|
|
<para>Some use cases that might indicate a need for a multi-site
|
|
deployment of OpenStack include:</para>
|
|
<itemizedlist>
|
|
<listitem>
|
|
<para>An organization with a diverse geographic
|
|
footprint.</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Geo-location sensitive data.</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Data locality, in which specific data or
|
|
functionality should be close to users.</para>
|
|
</listitem>
|
|
</itemizedlist>
|
|
|
|
<xi:include href="multi_site/section_user_requirements_multi_site.xml"/>
|
|
<xi:include href="multi_site/section_tech_considerations_multi_site.xml"/>
|
|
<xi:include href="multi_site/section_operational_considerations_multi_site.xml"/>
|
|
<xi:include href="multi_site/section_architecture_multi_site.xml"/>
|
|
<xi:include href="multi_site/section_prescriptive_examples_multi_site.xml"/>
|
|
|
|
</chapter>
|