The Quobyte volume driver enables storing Block Storage service volumes on a Quobyte storage back end. Block Storage service back ends are mapped to Quobyte volumes and individual Block Storage service volumes are stored as files on a Quobyte volume. Selection of the appropriate Quobyte volume is done by the aforementioned back end configuration that specifies the Quobyte volume explicitly.
Note
Note the dual use of the term volume
in the context of Block Storage
service volumes and in the context of Quobyte volumes.
For more information see the Quobyte support webpage.
The Quobyte volume driver supports the following volume operations:
Note
When running VM instances off Quobyte volumes, ensure that the Quobyte Compute service driver has been configured in your OpenStack cloud.
To activate the Quobyte volume driver, configure the corresponding
volume_driver
parameter:
volume_driver = cinder.volume.drivers.quobyte.QuobyteDriver
The following table contains the configuration options supported by the Quobyte driver:
Configuration option = Default value | Description |
---|---|
[DEFAULT] | |
quobyte_client_cfg = None |
(String) Path to a Quobyte Client configuration file. |
quobyte_mount_point_base = $state_path/mnt |
(String) Base dir containing the mount point for the Quobyte volume. |
quobyte_qcow2_volumes = True |
(Boolean) Create volumes as QCOW2 files rather than raw files. |
quobyte_sparsed_volumes = True |
(Boolean) Create volumes as sparse files which take no space. If set to False, volume is created as regular file.In such case volume creation takes a lot of time. |
quobyte_volume_url = None |
(URI) URL to the Quobyte volume e.g., quobyte://<DIR host>/<volume name> |
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.