
Follow the Documentaion conventions: https://wiki.openstack.org/wiki/Documentation/Conventions Change-Id: I16078f5bfc3c47002f43f23be83b03c1f6f938fe
102 lines
3.6 KiB
XML
102 lines
3.6 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<part version="5.0" xml:id="architecture"
|
|
xmlns="http://docbook.org/ns/docbook"
|
|
xmlns:xlink="http://www.w3.org/1999/xlink"
|
|
xmlns:xi="http://www.w3.org/2001/XInclude"
|
|
xmlns:ns5="http://www.w3.org/2000/svg"
|
|
xmlns:ns4="http://www.w3.org/1998/Math/MathML"
|
|
xmlns:ns3="http://www.w3.org/1999/xhtml"
|
|
xmlns:ns="http://docbook.org/ns/docbook">
|
|
<title>Architecture</title>
|
|
|
|
<partintro>
|
|
<para>Designing an OpenStack cloud is a great achievement. It requires a
|
|
robust understanding of the requirements and needs of the cloud's users to
|
|
determine the best possible configuration to meet them. OpenStack provides
|
|
a great deal of flexibility to achieve your needs, and this part of the
|
|
book aims to shine light on many of the decisions you need to make during
|
|
the process.</para>
|
|
|
|
<para>To design, deploy, and configure OpenStack, administrators must
|
|
understand the logical architecture. A diagram can help you envision all
|
|
the integrated services within OpenStack and how they interact with each
|
|
other.<indexterm class="singular">
|
|
<primary>modules, types of</primary>
|
|
</indexterm><indexterm class="singular">
|
|
<primary>OpenStack</primary>
|
|
|
|
<secondary>module types in</secondary>
|
|
</indexterm></para>
|
|
|
|
<para>OpenStack modules are one of the following types:</para>
|
|
|
|
<variablelist>
|
|
<varlistentry>
|
|
<term>Daemon</term>
|
|
|
|
<listitem>
|
|
<para>Runs as a background process. On Linux platforms, a daemon is
|
|
usually installed as a service.<indexterm class="singular">
|
|
<primary>daemons</primary>
|
|
|
|
<secondary>basics of</secondary>
|
|
</indexterm></para>
|
|
</listitem>
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
|
<term>Script</term>
|
|
|
|
<listitem>
|
|
<para>Installs a virtual environment and runs tests.<indexterm
|
|
class="singular">
|
|
<primary>script modules</primary>
|
|
</indexterm></para>
|
|
</listitem>
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
|
<term>Command-line interface (CLI)</term>
|
|
|
|
<listitem>
|
|
<para>Enables users to submit API calls to OpenStack services
|
|
through commands.<indexterm class="singular">
|
|
<primary>Command-line interface (CLI)</primary>
|
|
</indexterm></para>
|
|
</listitem>
|
|
</varlistentry>
|
|
</variablelist>
|
|
|
|
<para>As shown, end users can interact through the dashboard, CLIs, and
|
|
APIs. All services authenticate through a common Identity service, and
|
|
individual services interact with each other through public APIs, except
|
|
where privileged administrator commands are necessary. <xref
|
|
linkend="openstack-diagram" /> shows the most common, but not the
|
|
only logical architecture for an OpenStack cloud.</para>
|
|
<figure xml:id="openstack-diagram">
|
|
<title>OpenStack Logical Architecture (<link
|
|
xlink:href="http://docs.openstack.org/openstack-ops/content/figures/2/figures/osog_0001.png"
|
|
/>)</title>
|
|
<mediaobject>
|
|
<imageobject>
|
|
<imagedata fileref="http://git.openstack.org/cgit/openstack/operations-guide/plain/doc/openstack-ops/figures/osog_0001.png" width="6in"/>
|
|
</imageobject>
|
|
</mediaobject>
|
|
</figure>
|
|
</partintro>
|
|
|
|
<xi:include href="ch_arch_examples.xml" />
|
|
|
|
<xi:include href="ch_arch_provision.xml" />
|
|
|
|
<xi:include href="ch_arch_cloud_controller.xml" />
|
|
|
|
<xi:include href="ch_arch_compute_nodes.xml" />
|
|
|
|
<xi:include href="ch_arch_scaling.xml" />
|
|
|
|
<xi:include href="ch_arch_storage.xml" />
|
|
|
|
<xi:include href="ch_arch_network_design.xml" />
|
|
</part>
|