5fca287eb5
There are several instances of "Block Storage Service" in the upstream documentation. As was recently clarified in the docs mailing list, these should be "Block Storage service". This patch applies the fix. Change-Id: I591c100ab031b75f1c0d27d45f53e32401a26e30 Partial-Bug: #1217503
41 lines
1.8 KiB
XML
41 lines
1.8 KiB
XML
<section 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="block-storage-service">
|
|
<title>Block Storage</title>
|
|
<para>The Block Storage service enables management of volumes,
|
|
volume snapshots, and volume types. It includes the following
|
|
components:</para>
|
|
<itemizedlist>
|
|
<listitem>
|
|
<para><systemitem class="service">cinder-api</systemitem>:
|
|
Accepts API requests and routes them to <systemitem
|
|
class="service">cinder-volume</systemitem> for
|
|
action.</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para><systemitem class="service"
|
|
>cinder-volume</systemitem>: Responds to requests to read
|
|
from and write to the Block Storage database to maintain
|
|
state, interacting with other processes (like <systemitem
|
|
class="service">cinder-scheduler</systemitem>) through a
|
|
message queue and directly upon block storage providing
|
|
hardware or software. It can interact with a variety of
|
|
storage providers through a driver architecture.</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para><systemitem class="service"
|
|
>cinder-scheduler</systemitem> daemon: Like the
|
|
<systemitem class="service">nova-scheduler</systemitem>,
|
|
picks the optimal block storage provider node on which to
|
|
create the volume.</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Messaging queue: Routes information between the Block
|
|
Storage service processes.</para>
|
|
</listitem>
|
|
</itemizedlist>
|
|
<para>The Block Storage service interacts with Compute to
|
|
provide volumes for instances.</para>
|
|
</section>
|