Cinder Administration¶
The OpenStack Block Storage service works through the interaction of
a series of daemon processes named cinder-* that reside
persistently on the host machine or machines. You can run all the
binaries from a single node, or spread across multiple nodes. You can
also run them on the same node as other OpenStack services.
To administer the OpenStack Block Storage service, it is helpful to understand a number of concepts. You must make certain choices when you configure the Block Storage service in OpenStack. The bulk of the options come down to two choices - single node or multi-node install. You can read a longer discussion about Storage Decisions in the OpenStack Operations Guide.
OpenStack Block Storage enables you to add extra block-level storage to your OpenStack Compute instances. This service is similar to the Amazon EC2 Elastic Block Storage (EBS) offering.
- Security
- Accelerate image compression
- Increase Block Storage API service throughput
- Manage volumes
- Troubleshoot your installation
- Availability-zone types
- Generalized filters
- Back up Block Storage service disks
- Boot from volume
- Basic volume quality of service
- Capacity based quality of service
- Consistency groups
- Configure and use driver filter and weighing for scheduler
- Get capabilities
- User visible extra specs
- Generic volume groups
- Image-Volume cache
- Use LIO iSCSI support
- Configure multiple-storage back ends
- Configure an NFS storage back end
- Oversubscription in thin provisioning
- Rate-limit volume copy bandwidth
- Volume-backed image
- Export and import backup metadata
- Back up and restore volumes and snapshots
- Migrate volumes
- Volume multi-attach: Enable attaching a volume to multiple servers
- Configure and use volume number weigher
- Default Volume Types
- API Configuration
- Upgrades
