openstack/cinder
Code Issues Proposed changes
e05b261af7
cinder/doc/source/admin/blockstorage-manage-volumes.rst
Andreas Jaeger 99ec31f53f Docs: Make links more robust 
Some docs used external links which cannot be verified and thus we
easily might get broken links. Use internal links that Sphinx can verify.

Some additional updates:
* Update tox.ini to not publish the dirtrees.
* Update openstack mailing list to openstack-discuss
* Remove reference to not anymore existing 'OpenStack Configuration
  Reference'

Change-Id: I9a613fa682021fab7bbaba90b219adaa7d9384d3
2019-08-10 10:49:23 +02:00

3.0 KiB
Raw Blame History

Manage volumes

The default OpenStack Block Storage service implementation is an iSCSI solution that uses Logical Volume Manager (LVM) for Linux.

Note

The OpenStack Block Storage service also provides drivers that enable you to use several vendors' back-end storage devices in addition to the base LVM implementation. These storage devices can also be used instead of the base LVM installation.

This high-level procedure shows you how to create and attach a volume to a server instance.

To create and attach a volume to an instance

  1. Configure the OpenStack Compute and the OpenStack Block Storage services through the /etc/cinder/cinder.conf file.
  2. Use the openstack volume create command to create a volume. This command creates an LV into the volume group (VG) cinder-volumes.
  3. Use the openstack server add volume command to attach the volume to an instance. This command creates a unique IQN <iSCSI Qualified Name (IQN)> that is exposed to the compute node.
    • The compute node, which runs the instance, now has an active iSCSI session and new local storage (usually a /dev/sdX disk).
    • Libvirt uses that local storage as storage for the instance. The instance gets a new disk (usually a /dev/vdX disk).

For this particular walkthrough, one cloud controller runs nova-api, nova-scheduler, nova-conductor and cinder-* services. Two additional compute nodes run nova-compute. The walkthrough uses a custom partitioning scheme that carves out 60 GB of space and labels it as LVM. The network uses the FlatManager and NetworkManager settings for OpenStack Compute.

The network mode does not interfere with OpenStack Block Storage operations, but you must set up networking for Block Storage to work. For details, see networking.

To set up Compute to use volumes, ensure that Block Storage is installed along with lvm2. This guide describes how to troubleshoot your installation and back up your Compute volumes.

blockstorage-boot-from-volume.rst blockstorage-nfs-backend.rst blockstorage-multi-backend.rst blockstorage-backup-disks.rst blockstorage-volume-migration.rst blockstorage-volume-backups.rst blockstorage-volume-backups-export-import.rst blockstorage-lio-iscsi-support.rst blockstorage-volume-number-weigher.rst blockstorage-capacity-based-qos.rst blockstorage-consistency-groups.rst blockstorage-driver-filter-weighing.rst blockstorage-ratelimit-volume-copy-bandwidth.rst blockstorage-over-subscription.rst blockstorage-image-volume-cache.rst blockstorage-volume-backed-image.rst blockstorage-get-capabilities.rst blockstorage-groups.rst

Note

To enable the use of encrypted volumes, see the setup instructions in Create an encrypted volume type <create__encrypted_volume_type>.