openstack-manuals/doc/install-guide/basic-install-files/basic-install_architecture.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

95 lines
4.9 KiB
XML
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<?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="basic-install_architecture">
<title>Architecture</title>
<figure><title>Physical network diagram</title> <mediaobject>
<imageobject>
<imagedata width="6in" fileref="../../common/figures/Neutron-PhysNet-Diagram.png"/>
</imageobject>
<!-- Edit link: http://docs.google.com/drawings/d/19qtlB_EeG9TM_jpeX5DprHRd9ShngXgfpt_t5mlrUMo/edit -->
</mediaobject></figure>
<para>This guide creates the following types of OpenStack
servers:</para>
<itemizedlist>
<listitem>
<para><emphasis role="bold">The Cloud
Controller</emphasis>. Provides all functionality
of the cloud except actually hosting virtual machines
or providing network services. See the "Compute Node"
and "Network Controller" for details about those
roles. This server hosts the OpenStack Image
Service, Block Storage Service, Identity Service, and the
dashboard. It also runs portions of the OpenStack
Compute service, such as the API server, the scheduler,
conductor, console authenticator, and VNC service.
Finally, it hosts the API endpoint for the OpenStack
Network service.</para>
</listitem>
<listitem>
<para><emphasis role="bold">The Network
Controller</emphasis>. Provides the bulk of the
OpenStack Network services such as DHCP, layer 2
switching, layer 3 routing, floating IPs (which this
guide does not configure), and metadata connectivity.</para>
</listitem>
<listitem>
<para><emphasis role="bold">Compute Node</emphasis>. Runs
the OpenStack Compute service as well as the OpenStack
Network service agent (in this case, the Open vSwitch
plugin agent). This server also manages an
OpenStack-compatible hypervisor such as KVM or Xen.
This server hosts the actual virtual machines
(instances).</para>
</listitem>
</itemizedlist>
<note><para>OpenStack provides great flexibility with regard to how its
individual services can be hosted. For example, the services
that run on the Network Controller can easily be installed on
the Cloud Controller. As another example, the OpenStack Image
service can be installed on its own server (or many servers to
provide a more highly available service).</para>
</note>
<para>With regard to cloud networking, a standard OpenStack
Network setup can have up to four distinct physical data
center networks. Note that these networks can be combined and
re-used. For example, the Management, Data, and API networks
are commonly the same network. For simplicity, this guide shows this configuration.</para>
<itemizedlist>
<listitem>
<para><emphasis role="bold">Management
network</emphasis>. Used for internal
communication between OpenStack components. The IP
addresses on this network should be reachable only
within the data center.</para>
</listitem>
<listitem>
<para><emphasis role="bold">Data
network</emphasis>. Used for VM data communication
within the cloud deployment. The IP addressing
requirements of this network depend on the OpenStack
Networking plugin in use.</para>
</listitem>
<listitem>
<para><emphasis role="bold">External
network</emphasis>. Provides VMs with Internet
access in some deployment scenarios. The IP addresses
on this network should be reachable by anyone on the
Internet.</para>
</listitem>
<listitem>
<para><emphasis role="bold">API
network</emphasis>. Exposes all OpenStack APIs,
including the OpenStack Networking API, to
tenants. The IP addresses on this network should be
reachable by anyone on the Internet. This may be the
same network as the external network, as it is
possible to create a subnet for the external
network that uses IP allocation ranges to use only
less than the full range of IP addresses in an IP
block.</para>
</listitem>
</itemizedlist>
</chapter>