0abd3b14a6
- Converted section_ts_no_emulator_x86_64.xml - Fixed references in keystone_integrate_with_ldap.rst and keystone_integrate_identity_backend_ldap.rst Change-Id: Id9168f30553e45cfbe63412c4211679e20298a00 Implements: blueprint reorganise-user-guides
3.4 KiB
Block Storage
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. The binaries can all be
run from a single node, or spread across multiple nodes. They can also
be run 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.
blockstorage-api-throughput.rst blockstorage-manage-volumes.rst blockstorage-troubleshoot.rst
blockstorage_nfs_backend.rst blockstorage_glusterfs_backend.rst blockstorage_multi_backend.rst blockstorage_backup_disks.rst
Use LIO iSCSI support
The default mode for the iscsi_helper tool is
tgtadm. To use LIO iSCSI, install the
python-rtslib package, and set
iscsi_helper=lioadm in the cinder.conf file.
Once configured, you can use the cinder-rtstool command to manage the volumes. This
command enables you to create, delete, and verify volumes and determine
targets and add iSCSI initiators to the system.
Troubleshoot your installation
This section provides useful tips to help you troubleshoot your Block Storage installation.
ts_cinder_config.rst ts_vol_attach_miss_sg_scan.rst ts_non_existent_host.rst ts_non_existent_vlun.rst ts_no_emulator_x86_64.rst