![Akihiro Motoki](/assets/img/avatar_default.png)
Part of "consistency-file-rename" spec [1] This commit also changes the following: * Update corresponding references to common in various guides * Rename excluded_patterns in conf.py of various guide * Rename existing entries in www/static/.htaccess * Add entries to .htaccess to redirect renamed files [1] http://specs.openstack.org/openstack/docs-specs/specs/newton/consistency-file-rename.html Change-Id: I39a9d5b95535cad1918ee64e95dee5ef18ab2cbe
1.4 KiB
Block Storage service overview
The OpenStack Block Storage service (cinder) adds persistent storage to a virtual machine. Block Storage provides an infrastructure for managing volumes, and interacts with OpenStack Compute to provide volumes for instances. The service also enables management of volume snapshots, and volume types.
The Block Storage service consists of the following components:
- cinder-api
-
Accepts API requests, and routes them to the
cinder-volume
for action. - cinder-volume
-
Interacts directly with the Block Storage service, and processes such as the
cinder-scheduler
. It also interacts with these processes through a message queue. Thecinder-volume
service responds to read and write requests sent to the Block Storage service to maintain state. It can interact with a variety of storage providers through a driver architecture. - cinder-scheduler daemon
-
Selects the optimal storage provider node on which to create the volume. A similar component to the
nova-scheduler
. - cinder-backup daemon
-
The
cinder-backup
service provides backing up volumes of any type to a backup storage provider. Like thecinder-volume
service, it can interact with a variety of storage providers through a driver architecture. - Messaging queue
-
Routes information between the Block Storage processes.