Keystone Identity service<\/a> and other OpenStack services installed.<\/p>\nCinder Installation Guide <\/b><\/p>\n
The Block Storage service (cinder) 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 controller nodes, compute nodes, or standalone storage nodes. For more information, see the\u00a0Configuration Reference<\/i>.<\/p>\n
Prerequisites<\/b><\/p>\n
This documentation specifically covers the installation of the Cinder Block Storage service. Before fol- lowing this guide you will need to prepare your OpenStack environment using the instructions in the OpenStack Installation Guide.<\/p>\n
Once able to Launch an instance in your OpenStack environment follow the instructions below to add Cinder to the base environment.<\/p>\n
Adding Cinder to your OpenStack Environment<\/b><\/p>\n
The following links describe how to install the Cinder Block Storage Service:<\/p>\n
Cinder Block Storage service overview<\/b><\/p>\n
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:<\/p>\n
cinder-api\u00a0<\/b>Accepts API requests, and routes them to the cinder-volume for action.<\/p>\n
cinder-volume\u00a0<\/b>Interacts directly with the Block Storage service, and processes such as the cinder-scheduler. It also interacts with these processes through a message queue. The cinder-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.<\/p>\n
cinder-scheduler daemon\u00a0<\/b>Selects the optimal storage provider node on which to create the volume. A similar component to the nova-scheduler.<\/p>\n
cinder-backup daemon\u00a0<\/b>The cinder-backup service provides backing up volumes of any type to a backup storage provider. Like the cinder-volume service, it can interact with a variety of storage providers through a driver architecture.<\/p>\n","protected":false},"excerpt":{"rendered":"