openstack/openstack-manuals
Code Issues Proposed changes

Merge "General updates to Compute for style and convention"

Browse Source
This commit is contained in:
Jenkins
2015-01-22 05:43:32 +00:00
committed by Gerrit Code Review
parent 6429aed4f7 66355045d2
commit 72e0a45bb0
1 changed files with 39 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files

71
doc/admin-guide-cloud/ch_compute.xml
View File

@@ -143,7 +143,7 @@
<para>For tenants, you can use quota controls to limit the:</para> <para>For tenants, you can use quota controls to limit the:</para>
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para>Number of volumes that may be launched.</para> <para>Number of volumes that can be launched.</para>
</listitem> </listitem>
<listitem> <listitem>
<para>Number of processor cores and the amount of RAM that can be allocated.</para> <para>Number of processor cores and the amount of RAM that can be allocated.</para>
@@ -220,14 +220,17 @@
only one instance at a time, although you can detach and only one instance at a time, although you can detach and
reattach volumes to as many different instances as you reattach volumes to as many different instances as you
like.</para> like.</para>
<para>You can configure persistent volumes as bootable and use them to provide a persistent <para>You can configure persistent volumes as bootable and use
virtual instance similar to traditional non-cloud-based virtualization systems. them to provide a persistent virtual instance similar to
Typically, the resulting instance can also still have ephemeral storage depending on the traditional non-cloud-based virtualization systems.
flavor selected, but the root file system can be on the persistent volume and its state It is still possible for the resulting instance to also have
maintained even if the instance is shut down. For more information about this type of ephemeral storage, depending on the flavor selected. In this
configuration, see the <link case, the root file system can be on the persistent volume
xlink:href="http://docs.openstack.org/juno/config-reference/content/"> and its state maintained even if the instance is shut down.
<citetitle>OpenStack Configuration Reference</citetitle></link>. For more information about this type of configuration, see
the <link
xlink:href="http://docs.openstack.org/juno/config-reference/content/">
<citetitle>OpenStack Configuration Reference</citetitle></link>.
</para> </para>
<note> <note>
<para>Persistent volumes do not provide concurrent access <para>Persistent volumes do not provide concurrent access
@@ -241,13 +244,13 @@
</section> </section>
<section xml:id="instance-mgmt-ec2compat"> <section xml:id="instance-mgmt-ec2compat">
<title>EC2 compatibility API</title> <title>EC2 compatibility API</title>
<para>In addition to the native compute API, OpenStack provides an EC2-compatible API. This <para>In addition to the native compute API, OpenStack provides
API allows EC2 legacy workflows built for EC2 to work with OpenStack. The an EC2-compatible API. This API allows EC2 legacy workflows
<link built for EC2 to work with OpenStack. For more information and
xlink:href="http://docs.openstack.org/juno/config-reference/content/"> configuration options about this compatibility API, see the <link
<citetitle>OpenStack Configuration Reference</citetitle></link> xlink:href="http://docs.openstack.org/juno/config-reference/content/">
lists configuration options <citetitle>OpenStack Configuration Reference</citetitle></link>.
for customizing this compatibility API on your OpenStack cloud.</para> </para>
<para>Numerous third-party tools and language-specific SDKs <para>Numerous third-party tools and language-specific SDKs
can be used to interact with OpenStack clouds, using both can be used to interact with OpenStack clouds, using both
native and compatibility APIs. Some of the more popular native and compatibility APIs. Some of the more popular
@@ -392,13 +395,13 @@
</section> </section>
<section xml:id="section_compute-service-arch"> <section xml:id="section_compute-service-arch">
<title>Compute service architecture</title> <title>Compute service architecture</title>
<para>The following basic categories describe the service architecture and what's going <para>These basic categories describe the service
on within the cloud controller.</para> architecture and information about the cloud controller.</para>
<simplesect> <simplesect>
<title>API server</title> <title>API server</title>
<para>At the heart of the cloud framework is an API server. This API server makes <para>At the heart of the cloud framework is an API server,
command and control of the hypervisor, storage, and networking programmatically which makes command and control of the hypervisor, storage,
available to users.</para> and networking programmatically available to users.</para>
<para>The API endpoints are basic HTTP web services <para>The API endpoints are basic HTTP web services
which handle authentication, authorization, and which handle authentication, authorization, and
basic command and control functions using various basic command and control functions using various
@@ -417,19 +420,23 @@
infrastructure), API endpoints, the scheduler infrastructure), API endpoints, the scheduler
(determines which physical hardware to allocate to (determines which physical hardware to allocate to
a virtual resource), and similar components. a virtual resource), and similar components.
Communication to and from the cloud controller is Communication to and from the cloud controller is handled
by HTTP requests through multiple API by HTTP requests through multiple API
endpoints.</para> endpoints.</para>
<para>A typical message passing event begins with the API server receiving a request <para>A typical message passing event begins with the API
from a user. The API server authenticates the user and ensures that the user is server receiving a request from a user. The API server
permitted to issue the subject command. The availability of objects implicated in authenticates the user and ensures that they are permitted
the request is evaluated and, if available, the request is routed to the queuing to issue the subject command. The availability of objects
engine for the relevant workers. Workers continually listen to the queue based on implicated in the request is evaluated and, if available,
their role, and occasionally their type host name. When an applicable work request the request is routed to the queuing engine for the
arrives on the queue, the worker takes assignment of the task and begins its relevant workers. Workers continually listen to the queue
execution. Upon completion, a response is dispatched to the queue which is received based on their role, and occasionally their type host name.
by the API server and relayed to the originating user. Database entries are queried, When an applicable work request arrives on the queue, the
added, or removed as necessary throughout the process.</para> worker takes assignment of the task and begins executing it.
Upon completion, a response is dispatched to the queue
which is received by the API server and relayed to the
originating user. Database entries are queried, added, or
removed as necessary during the process.</para>
</simplesect> </simplesect>
<simplesect> <simplesect>
<title>Compute worker</title> <title>Compute worker</title>