20d15b80df
Use the common documentation glossary. Move entries from ch_glossary to the common documentation glossary and add glossterm so that the entry gets displayed in the glossary. Remove entries from the Arch Design specific glossary that are fully explained in the text. Remove entries that are already in the common glossary and add glossterm for them in the text. Add glossary as final chapter to the manual. The remaining glossary entries need some further discussion. Change-Id: Ic82ae5235e1306fc13be81fa4971710321da5072
75 lines
3.1 KiB
XML
75 lines
3.1 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="specialized">
|
|
<title>Specialized cases</title>
|
|
|
|
<para>Although most OpenStack architecture designs fall into one
|
|
of the seven major scenarios outlined in other sections
|
|
(compute focused, network focused, storage focused, general
|
|
purpose, multi-site, hybrid cloud, and massively scalable),
|
|
there are a few other use cases that are unique enough they
|
|
can't be neatly categorized into one of the other major
|
|
sections. This section discusses some of these unique use
|
|
cases with some additional details and design considerations
|
|
for each use case:</para>
|
|
<itemizedlist>
|
|
<listitem>
|
|
<para>
|
|
<link
|
|
linkend="specialized-networking-example">Specialized
|
|
Networking</link>: This describes running
|
|
networking-oriented software that may involve reading
|
|
packets directly from the wire or participating in
|
|
routing protocols.
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>
|
|
<link
|
|
linkend="software-defined-networking-sdn">Software-defined
|
|
networking (SDN)</link>: This use case details both
|
|
running an SDN controller from within OpenStack as well
|
|
as participating in a software-defined network.
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>
|
|
<link
|
|
linkend="desktop-as-a-service"><glossterm>Desktop-as-a-Service</glossterm></link>:
|
|
This is for organizations that want to run a virtualized
|
|
desktop environment on a cloud. This can apply to
|
|
private or public clouds.
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>
|
|
<link
|
|
linkend="arch-guide-openstack-on-openstack">OpenStack on
|
|
OpenStack</link>: Some organizations are finding that it
|
|
makes technical sense to build a multi-tiered cloud by
|
|
running OpenStack on top of an OpenStack
|
|
installation.
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>
|
|
<link linkend="specialized-hardware">Specialized
|
|
hardware</link>: Some highly specialized situations will
|
|
require the use of specialized hardware devices from
|
|
within the OpenStack environment.
|
|
</para>
|
|
</listitem>
|
|
</itemizedlist>
|
|
|
|
<xi:include href="specialized/section_multi_hypervisor_specialized.xml"/>
|
|
<xi:include href="specialized/section_networking_specialized.xml"/>
|
|
<xi:include href="specialized/section_software_defined_networking_specialized.xml"/>
|
|
<xi:include href="specialized/section_desktop_as_a_service_specialized.xml"/>
|
|
<xi:include href="specialized/section_openstack_on_openstack_specialized.xml"/>
|
|
<xi:include href="specialized/section_hardware_specialized.xml"/>
|
|
|
|
</chapter>
|