openstack-manuals/doc/install-guide/ch_overview.xml
Matt Kassawara 9bce275711 Clarified example architectures
Updated the associated 'master' patch after review cycle changes to
the 'havana' patch.

Change-Id: I5ab35042afdb4c76490b5a1c460e875c11ea24d8
Partial-Bug: #1263719
2014-01-13 07:46:00 -07:00

105 lines
4.7 KiB
XML

<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="ch_overview">
<?dbhtml stop-chunking?>
<title>Architecture</title>
<para>This install guide offers a few of the many ways to install
OpenStack components and have them work together. It is meant as a
"choose your own adventure" guide, not a comprehensive guide. The
<citetitle>OpenStack Configuration Reference</citetitle> lists
every option in all OpenStack services. Before you begin an
installation adventure, here are some things you should know about
OpenStack concepts.</para>
<xi:include href="../common/ch_getstart.xml"
xpointer="element(para1)"/>
<xi:include href="../common/ch_getstart.xml"
xpointer="element(para2)"/>
<xi:include href="../common/ch_getstart.xml"
xpointer="element(para3)"/>
<xi:include href="../common/ch_getstart.xml"
xpointer="element(table1)"/>
<xi:include href="../common/section_getstart_conceptual_arch.xml"/>
<xi:include href="../common/section_getstart_logical_arch.xml"/>
<section xml:id="overview-architecture">
<title>Example architectures</title>
<para>This guide enables you to choose your own OpenStack
adventure. OpenStack is highly configurable to meet different
needs with various compute, networking, and storage options.</para>
<para>This guide uses the following example architectures:</para>
<itemizedlist>
<listitem>
<para>Basic architecture with legacy networking</para>
<itemizedlist>
<listitem>
<para>The controller node runs the Identity Service, Image Service,
dashboard, and management portion of Compute. It also contains
the associated API services, MySQL databases, and messaging
system.</para>
</listitem>
<listitem>
<para>The compute node runs the hypervisor portion of Compute,
which operates tenant virtual machines. By default, Compute uses
KVM as the hypervisor. Compute also provisions and operates
tenant networks and implements security groups. You can run more
than one compute node.</para>
</listitem>
<listitem>
<para>When implementing this architecture, skip
<xref linkend="ch_neutron" />.</para>
</listitem>
</itemizedlist>
<figure xml:id="basic-architecture-with-legacy-networking">
<title>Basic architecture with legacy networking</title>
<mediaobject>
<imageobject>
<imagedata contentwidth="6in"
fileref="figures/basic-architecture.svg"/>
</imageobject>
</mediaobject>
</figure>
</listitem>
<listitem>
<para>Basic architecture with OpenStack Networking (Neutron)</para>
<itemizedlist>
<listitem>
<para>The controller node runs the Identity Service, Image Service,
dashboard, and management portions of Compute and Networking.
It also contains the associated API services, MySQL databases,
and messaging system.</para>
</listitem>
<listitem>
<para>The network node runs the Networking plug-in agent and
several layer 3 agents that provision tenant networks and
provide services to them, including routing, NAT, and DHCP.
It also handles external (internet) connectivity for tenant
virtual machines.</para>
</listitem>
<listitem>
<para>The compute node runs the hypervisor portion of Compute,
which operates tenant virtual machines. By default, Compute uses
KVM as the hypervisor. The compute node also runs the Networking
plug-in agent, which operates tenant networks and implements
security groups. You can run more than one compute node.</para>
</listitem>
<listitem>
<para>When implementing this architecture, skip
<xref linkend="nova-network" />.</para>
</listitem>
</itemizedlist>
<figure xml:id="basic-architecture-with-virtual-networking">
<title>Basic architecture with OpenStack Networking (Neutron)</title>
<mediaobject>
<imageobject>
<imagedata contentwidth="5in"
fileref="../common/figures/Neutron-PhysNet-Diagram.png"/>
</imageobject>
</mediaobject>
</figure>
</listitem>
</itemizedlist>
<para>You can add nodes that run Block Storage or Object Storage to
either of these architectures.</para>
</section>
</chapter>