diff --git a/doc/common/section_getstart_image.xml b/doc/common/section_getstart_image.xml
index f8a5fd0b94..20d87599f6 100644
--- a/doc/common/section_getstart_image.xml
+++ b/doc/common/section_getstart_image.xml
@@ -23,12 +23,10 @@
use MySQL or SQlite.
- Storage repository for image files. In , the Object Storage Service is
- the image repository. However, you can configure a different
- repository. The Image Service supports normal file systems,
- RADOS block devices, Amazon S3, and HTTP. Some choices provide
- only read-only usage.
+ Storage repository for image files. The Image Service
+ supports a variety of repositories including normal file systems,
+ Object Storage, RADOS block devices, HTTP, and Amazon S3. Some
+ types of repositories support only read-only usage.A number of periodic processes run on the Image Service to
diff --git a/doc/install-guide/ch_overview.xml b/doc/install-guide/ch_overview.xml
index 7a2ec8a55f..dbacaba753 100644
--- a/doc/install-guide/ch_overview.xml
+++ b/doc/install-guide/ch_overview.xml
@@ -8,113 +8,146 @@
We are updating this material for Icehouse. You may find structure
and/or content issues during this process.
- 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
- OpenStack Configuration Reference lists
- every option in all OpenStack services. Before you begin an
- installation adventure, here are some things you should know about
- OpenStack concepts.
-
-
-
-
-
-
-
+
+ Overview
+ The OpenStack project is an open source cloud
+ computing platform that supports all types of cloud environments. The
+ project aims for simple implementation, massive scalability, and a rich
+ set of features. Cloud computing experts from around the world
+ contribute to the project.
+ OpenStack provides an Infrastructure-as-a-Service
+ (IaaS) solution through a variety of complemental
+ services. Each service offers an application programming interface
+ (API) that facilitates this integration. The
+ following table provides a list of OpenStack services:
+
+ This guide describes how to deploy these services in a functional
+ test environment and, by example, teaches you how to build a production
+ environment.
+
+
+ Conceptual architecture
+ Launching a virtual machine or instance involves many interactions
+ among several services. The following diagram provides the conceptual
+ architecture of a typical OpenStack environment.
+
+
+ Example architectures
- 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.
- This guide uses the following example architectures:
+ OpenStack is highly configurable to meet different needs with various
+ compute, networking, and storage options. This guide enables you to
+ choose your own OpenStack adventure using a combination of basic and
+ optional services. This guide uses the following example
+ architectures:
- Basic architecture with legacy networking
+ Two-node architecture with legacy networking. See .
- 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.
+ The basic
+ controller node
+ runs the Identity service, Image Service, management portion of
+ Compute, and the dashboard necessary to launch a simple instance.
+ It also includes supporting services such as MySQL,
+ AMQP, and
+ NTP.
+ Optionally, the controller node also runs portions of
+ Block Storage, Object Storage, Database Service, Orchestration,
+ and Telemetry. These components provide additional features for
+ your environment.
- The compute node runs the
+ The basic compute node runs the
hypervisor portion of Compute,
which operates tenant
- virtual machines.
- By default, Compute uses
+ virtual machines
+ or instances. By default, Compute uses
KVM
as the hypervisor. Compute also
- provisions and operates
- tenant networks and implements
+ provisions and operates tenant networks and implements
security groups.
You can run more than one compute node.
-
-
- When implementing this architecture, skip
- .
+ Optionally, the compute node also runs the Telemetry
+ agent. This component provides additional features for
+ your environment.
-
- Basic architecture with OpenStack Networking (Neutron)
+ Three-node architecure with OpenStack Networking (neutron). See .
- 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.
+ The basic controller node runs the Identity service, Image
+ Service, management portions of Compute and Networking,
+ Networking plug-in, and the dashboard. It also includes
+ supporting services such as MySQL, AMQP, and NTP.
+ Optionally, the controller node also runs portions of
+ Block Storage, Object Storage, Database Service, Orchestration,
+ and Telemetry. These components provide additional features for
+ your environment.
- 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.
+ The network node runs the Networking plug-in, layer 2 agent,
+ and several layer 3 agents that provision and operate tenant
+ networks. Layer 2 services include provisioning of virtual
+ networks and tunnels. Layer 3 services include routing,
+ NAT
+ , and DHCP. This node also handles
+ external (internet) connectivity for tenant virtual machines
+ or instances.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.
-
-
- When implementing this architecture, skip
- .
+ which operates tenant virtual machines or instances. By default
+ Compute uses KVM as the hypervisor. The compute node also runs
+ the Networking plug-in and layer 2 agent which operate tenant
+ networks and implement security groups. You can run more than
+ one compute node.
+ Optionally, the compute node also runs the Telemetry
+ agent. This component provides additional features for
+ your environment.
-
- Basic architecture with OpenStack Networking (Neutron)
+
+ When you implement this architecture, skip
+ in .
+ To use optional services, you might need to install additional
+ nodes, as described in subsequent chapters.
+
+
+ Three-node architecture with OpenStack Networking (neutron)
-
+
- You can add nodes that run Block Storage or Object Storage to
- either of these architectures.
diff --git a/doc/install-guide/figures/installguide_arch-neutron.png b/doc/install-guide/figures/installguide_arch-neutron.png
new file mode 100644
index 0000000000..4186cc54e6
Binary files /dev/null and b/doc/install-guide/figures/installguide_arch-neutron.png differ
diff --git a/doc/install-guide/figures/installguide_arch-neutron.svg b/doc/install-guide/figures/installguide_arch-neutron.svg
new file mode 100644
index 0000000000..c9f38e307e
--- /dev/null
+++ b/doc/install-guide/figures/installguide_arch-neutron.svg
@@ -0,0 +1,986 @@
+
+
+
+
diff --git a/doc/install-guide/figures/installguide_arch-nova.png b/doc/install-guide/figures/installguide_arch-nova.png
new file mode 100644
index 0000000000..fd28070944
Binary files /dev/null and b/doc/install-guide/figures/installguide_arch-nova.png differ
diff --git a/doc/install-guide/figures/installguide_arch-nova.svg b/doc/install-guide/figures/installguide_arch-nova.svg
new file mode 100644
index 0000000000..06b0073c62
--- /dev/null
+++ b/doc/install-guide/figures/installguide_arch-nova.svg
@@ -0,0 +1,731 @@
+
+
+
+