openstack/operations-guide
Code Issues Proposed changes

Address O'Reilly edits for chapter 3

Browse Source 
Change-Id: I8f52119e72d4aeddf0712a05a2b9effd8f695976
This commit is contained in:
Anne Gentle 2014-02-13 16:32:00 -06:00
parent c29136d03a
commit 6a6db7b848
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
doc/openstack-ops/ch_arch_cloud_controller.xml
View File

@ -16,18 +16,18 @@
allows all services to be distributed widely. However, to simplify this allows all services to be distributed widely. However, to simplify this
guide we have decided to discuss services of a more central nature using guide we have decided to discuss services of a more central nature using
the concept of a <emphasis>cloud controller</emphasis>. A cloud the concept of a <emphasis>cloud controller</emphasis>. A cloud
controller is just a conceptual simplification, and in the real world controller is just a conceptual simplification. In the real world
you likely will design an architecture for your cloud controller that you design an architecture for your cloud controller that enables
enables high availability so the cloud controller tasks are spread out high availability. In reality, the cloud controller tasks are spread out
across more than a single node. The cloud controller provides the across more than a single node. The cloud controller provides the
central management system for OpenStack deployments. Typically the cloud central management system for OpenStack deployments. Typically the
controller manages authentication and sends messaging to all the systems cloud controller manages authentication and sends messaging to all the
through a message queue.</para> systems through a message queue.</para>
<para>For more details about an overall example architecture, see the <xref <tip><para>For a more detailed example architecture, see
linkend="example_architecture"/>.</para> <xref linkend="example_architecture"/>.</para></tip>
<para>For many deployments, the cloud controller is a single node, but for <para>For many deployments, the cloud controller is a single node, but for
high availability, you have considerations about the design to explore high availability, you have considerations about the design to explore
further in this chapter. The concept of a cloud controller hosts these further in this chapter. The cloud controller provides these
necessary management services for the cloud:</para> necessary management services for the cloud:</para>
<itemizedlist> <itemizedlist>
<listitem> <listitem>