From 375b65665823b947186d7a48270aaf3831671aa2 Mon Sep 17 00:00:00 2001 From: dotalton Date: Fri, 27 Feb 2015 16:53:03 -0500 Subject: [PATCH] Clarified and added more information on storage drivers. 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 --- doc/install-guide/ch_cinder.xml | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/doc/install-guide/ch_cinder.xml b/doc/install-guide/ch_cinder.xml index fa843404c2..6776595d04 100644 --- a/doc/install-guide/ch_cinder.xml +++ b/doc/install-guide/ch_cinder.xml @@ -6,13 +6,16 @@ xml:id="ch_cinder"> Add the Block Storage service 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 - Configuration Reference. + 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 + + Configuration Reference. This chapter omits the backup manager because it depends on the Object Storage service.