![dotalton](/assets/img/avatar_default.png)
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
34 lines
1.7 KiB
XML
34 lines
1.7 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<chapter xmlns="http://docbook.org/ns/docbook"
|
|
xmlns:xi="http://www.w3.org/2001/XInclude"
|
|
xmlns:xlink="http://www.w3.org/1999/xlink"
|
|
version="5.0"
|
|
xml:id="ch_cinder">
|
|
<title>Add the Block Storage service</title>
|
|
<para>The OpenStack Block Storage service provides block storage devices
|
|
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>
|
|
</note>
|
|
<xi:include href="../common/section_getstart_block-storage.xml"/>
|
|
<xi:include href="section_cinder-controller-node.xml"/>
|
|
<xi:include href="section_cinder-storage-node.xml"/>
|
|
<xi:include href="section_cinder-verify.xml"/>
|
|
<section xml:id="section_cinder_next_steps">
|
|
<title>Next steps</title>
|
|
<para>Your OpenStack environment now includes Block Storage. You can
|
|
<link linkend="launch-instance">launch an instance</link> or add more
|
|
services to your environment in the following chapters.</para>
|
|
</section>
|
|
</chapter>
|