The following volume type extra specs are now visible to regular users (non-administrators): - RESKEY:availability_zones - multiattach - replication_enabled The list is defined in the code, and is not configurable. Regular users may view these user visible specs, and use them as a filter when listing volume types, but access is essentially read-only. Only cloud administrators are authorized to create or modify extra specs, including the user visible ones. The feature works by relaxing a few policies that were previously admin-only, and adds a new volume_extension:types_extra_specs:read_sensitive policy that limits access to all other (non-user visible) specs so that only cloud administrators can see them. DocImpact Implements: bp expose-user-visible-extra-specs Change-Id: I5434ea4199cce8158b75771fb6127be001baf328
3.0 KiB
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
- Configure the OpenStack Compute and the OpenStack Block Storage
services through the
/etc/cinder/cinder.conf
file. - Use the
openstack volume create
command to create a volume. This command creates an LV into the volume group (VG)cinder-volumes
. - Use the
openstack server add volume
command to attach the volume to an instance. This command creates a uniqueIQN <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).
- The compute node, which runs the instance, now has an active iSCSI
session and new local storage (usually a
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-user-visible-extra-specs.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>
.