The Cinder of OpenStack

First, cinder Overview:

1, before the F version, there is no cinder, the corresponding component is nova-volume; provide services in the form of rest APIs

2. Cinder Target:

Reduce the complexity of nova, reduce the load on Nova, support multiple back-end storage, and increase interaction with other components;

Back-end storage includes isics and ceph, etc.;

　　Cinder provides a backend storage adapter, rather than implementing a storage system;

Provide block storage, virtual machine disk;

3, API Service: Responsible for receiving and processing rest requests, and put the request into the rabbitmq/qpid queue;

4. Scheduler Service

Handle task queue tasks, and select the appropriate volume service node according to the predetermined policy to perform the task;

5. Volume Service:

The service runs on the storage node and manages the storage space;

Second, cinder storage solution:

1, using local storage, that is cinder LFS

2. Using a dynamic storage system, i.e. cinder ZFS

This solution solves a variety of storage features, such as:

Cache, Copy on Write, Snapshot&clone, changeable block size

3, the use of distributed storage system, that is, cinder DFS,

Common Distributed Storage systems:

Ceph, Sheepdog, Glusterfs

The Cinder of OpenStack