Flavien Hardy 32772164ea [config-ref] Add caution note about auto reactivation volumes for LVM driver

Add a note to prevent configuration conflict in lvm.conf about
auto_activation_volumes_list. If this option is defined without cinder volume
group into the list, then cinder volumes can't be automatically
reactivated after volume extension.
This configuration issue doesn't involve volumes without linked snapshots or
thinly provisioned volumes.

Change-Id: I29165468b7e52ce6296c2d200f132213fad69e00
Closes-Bug: #1479208

2016-08-26 11:19:36 +02:00

1.2 KiB

Raw Blame History

LVM

The default volume back end uses local volumes managed by LVM.

This driver supports different transport protocols to attach volumes, currently iSCSI and iSER.

Set the following in your cinder.conf configuration file, and use the following options to configure for iSCSI transport:

volume_driver = cinder.volume.drivers.lvm.LVMVolumeDriver
iscsi_protocol = iscsi

Use the following options to configure for the iSER transport:

volume_driver = cinder.volume.drivers.lvm.LVMVolumeDriver
iscsi_protocol = iser

Caution

When extending an existing volume which has a linked snapshot, the related logical volume is deactivated. This logical volume is automatically reactivated unless auto_activation_volume_list is defined in LVM configuration file lvm.conf. See the lvm.conf file for more information.

If auto activated volumes are restricted, then include the cinder volume group into this list:

auto_activation_volume_list = [ "existingVG", "cinder-volumes" ]

This note does not apply for thinly provisioned volumes because they do not need to be deactivated.

1.2 KiB Raw Blame History

LVM

1.2 KiB

Raw Blame History