openstack/openstack-manuals
Code Issues Proposed changes

Clarified and added more information on storage drivers.

Browse Source 
Updated this to reflect the availability of multiple storage
backends, and how backends work in general. Added exaples of backends.
Explain how the backend could determine where you are able to run
the cinder volume service.

Change-Id: If5d8ee2a1111c6450fe0b9a6a5b147137a963f3d
This commit is contained in:
dotalton 2015-02-27 16:53:03 -05:00
parent ca9eab16ec
commit 375b656658
1 changed files with 10 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
doc/install-guide/ch_cinder.xml
View File

@ -6,13 +6,16 @@
xml:id="ch_cinder">
<title>Add the Block Storage service</title>
<para>The OpenStack Block Storage service provides block storage devices
to instances using various backends. The Block Storage API and scheduler
services run on the controller node and the volume service runs on one
or more storage nodes. Storage nodes provide volumes to instances using
local block storage devices or SAN/NAS backends with the appropriate
drivers. For more information, see the
<link xlink:href="http://docs.openstack.org/juno/config-reference/content/section_volume-drivers.html"
><citetitle>Configuration Reference</citetitle></link>.</para>
to guest instances. The method in which the storage is provisioned and
consumed is determined by the Block Storage driver, or drivers
in the case of a multi-backend configuration. There are a variety of
drivers that are available: NAS/SAN, NFS, iSCSI, Ceph, and more.
The Block Storage API and scheduler services typically run on the controller
nodes. Depending upon the drivers used, the volume service can run
on controllers, compute nodes, or standalone storage nodes.
For more information, see the
<link xlink:href="http://docs.openstack.org/juno/config-reference/content/section_volume-drivers.html">
<citetitle>Configuration Reference</citetitle></link>.</para>
<note>
<para>This chapter omits the backup manager because it depends on the
Object Storage service.</para>