
We keep seeing people concerned about data leakage and thorough deletion of data from volumes on volume deletion [1][2], and Cinder currently only worries about the data leakage, not the stealing of the physical disks. In order to clarify this for administrators and to reduce the number of specs proposed to address this issue we are adding additional documentation on security aspects as well as data leakage. This patch was decided as an action from the discussion during the Wallaby PTG [3]. [1]: https://review.opendev.org/#/c/758375/ [2]: https://review.opendev.org/#/c/759553/ [3]: https://wiki.openstack.org/wiki/CinderWallabyPTGSummary#Two_proposed_specs_on_the_same_topic_.28mutually_assured_destruction.29 Change-Id: I9f8d413cf8337e75241ad24c85692135b34a17fc Implements: blueprint specify-data-secure-deletion
37 lines
909 B
ReStructuredText
37 lines
909 B
ReStructuredText
.. _volume-drivers:
|
|
|
|
==============
|
|
Volume drivers
|
|
==============
|
|
|
|
To use different volume drivers for the cinder-volume service, use the
|
|
parameters described in these sections.
|
|
|
|
These volume drivers are included in the `Block Storage repository
|
|
<https://opendev.org/openstack/cinder>`_. To set a volume
|
|
driver, use the ``volume_driver`` flag.
|
|
|
|
The default is:
|
|
|
|
.. code-block:: ini
|
|
|
|
volume_driver = cinder.volume.drivers.lvm.LVMVolumeDriver
|
|
|
|
Note that some third party storage systems may maintain more detailed
|
|
configuration documentation elsewhere. Contact your vendor for more information
|
|
if needed.
|
|
|
|
Driver Configuration Reference
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
.. sort by the drivers by open source software
|
|
.. and the drivers for proprietary components
|
|
|
|
.. toctree::
|
|
:glob:
|
|
:maxdepth: 1
|
|
|
|
drivers/ceph-rbd-volume-driver
|
|
drivers/lvm-volume-driver
|
|
drivers/nfs-volume-driver
|
|
drivers/*
|