openstack-manuals/doc/install-guide/section_example-installation-arch.xml
Diane Fleming 64b6c9261e Folder rename, file rename, flattening of directories
Current folder name	New folder name	        Book title
----------------------------------------------------------
basic-install 	        DELETE
cli-guide	        DELETE
common	                common
NEW	                admin-guide-cloud	Cloud Administrators Guide
docbkx-example	        DELETE
openstack-block-storage-admin 	DELETE
openstack-compute-admin 	DELETE
openstack-config 	config-reference	OpenStack Configuration Reference
openstack-ha 	        high-availability-guide	OpenStack High Availabilty Guide
openstack-image	        image-guide	OpenStack Virtual Machine Image Guide
openstack-install 	install-guide	OpenStack Installation Guide
openstack-network-connectivity-admin 	admin-guide-network 	OpenStack Networking Administration Guide
openstack-object-storage-admin 	DELETE
openstack-security 	security-guide	OpenStack Security Guide
openstack-training 	training-guide	OpenStack Training Guide
openstack-user 	        user-guide	OpenStack End User Guide
openstack-user-admin 	user-guide-admin	OpenStack Admin User Guide
glossary	        NEW        	OpenStack Glossary

bug: #1220407

Change-Id: Id5ffc774b966ba7b9a591743a877aa10ab3094c7
author: diane fleming
2013-09-08 15:15:50 -07:00

70 lines
3.3 KiB
XML

<?xml version="1.0" encoding="UTF-8"?>
<section
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="example-installation-architecture">
<title>Example Installation Architectures</title>
<para>OpenStack Compute uses a shared-nothing, messaging-based
architecture. While very flexible, the fact that you can install each
nova- service on an independent server means there are many possible
methods for installing OpenStack Compute. Here are the types of
installation architectures:</para>
<itemizedlist>
<listitem>
<para>Single node: Only one server runs all nova- services and also
drives all the virtual instances. Use this configuration only for
trying out OpenStack Compute, or for development purposes.</para>
</listitem>
<listitem>
<para>Two nodes: A cloud controller node runs the nova- services
except for <systemitem class="service">nova-compute</systemitem>, and a compute node runs
<systemitem class="service">nova-compute</systemitem>. A client computer is likely needed to
bundle images and interfacing to the servers, but a client is not
required. Use this configuration for proof of concepts or development
environments.</para>
</listitem>
<listitem>
<para>Multiple nodes: You can add more compute nodes to the two node
installation by simply installing <systemitem class="service">nova-compute</systemitem> on
an additional server and copying a <filename>nova.conf</filename> file
to the added node. This would result in a multiple node installation.
You can also add a volume controller and a network controller as
additional nodes in a more complex multiple node installation. A
minimum of 4 nodes is best for running multiple virtual instances that
require a lot of processing power.</para>
</listitem>
</itemizedlist>
<para>This is an illustration of one possible multiple server installation
of OpenStack Compute. Virtual server networking in the cluster may
vary.</para>
<para><inlinemediaobject>
<imageobject>
<imagedata fileref="figures/NOVA_install_arch.png" scale="80"/>
</imageobject>
</inlinemediaobject></para>
<para>An alternative architecture would be to add more messaging servers if you notice a lot of
back up in the messaging queue causing performance problems. In that case you would add an
additional messaging server in addition to or instead of scaling up the database server.
Your installation can run any nova- service on any server as long as the
<filename>nova.conf</filename> is configured to point to the messaging server and the
server can send messages to the server.</para>
<para>Multiple installation architectures are possible, here is another
example illustration.</para>
<para><inlinemediaobject>
<imageobject>
<imagedata fileref="figures/NOVA_compute_nodes.png" scale="40"/>
</imageobject>
</inlinemediaobject></para>
</section>