Openstack Charmers Next Cinder Lvm

  • By OpenStack Charmers - Testing Charms
  • Cloud
juju deploy openstack-charmers-next-cinder-lvm
Show information
You will need Juju 2.9 to be able to run this command. Learn how to upgrade to Juju 2.9.
Channel Version Revision Published Runs on
latest/stable 8 8 23 Nov 2021
Ubuntu 21.10 Ubuntu 21.04 Ubuntu 20.10 Ubuntu 20.04 Ubuntu 18.04


18.04 20.04 20.10 21.04 21.10


LVM integration for OpenStack Block Storage Read more

Relevant links

Discuss this charm

Share your thoughts on this charm with the community on discourse.

Join the discussion


The cinder-lvm charm provides an LVM backend for Cinder, the core OpenStack block storage (volume) service. It is a subordinate charm that is used in conjunction with the cinder charm.

Note: The cinder-lvm charm is supported starting with OpenStack Queens.



This section covers common and/or important configuration options. See file config.yaml for the full list of options, along with their descriptions and default values. See the Juju documentation for details on configuring applications.


Refers to volume provisioning type. Values can be 'thin', 'thick', 'auto' (resolves to 'thin' if supported) , and 'default' (resolves to 'thick'). The default value is 'default'.


Specifies a space-separated list of devices to use for LVM physical volumes. This is a mandatory option. Value types include:

  • block devices (e.g. 'sdb' or '/dev/sdb')
  • a path to a local file with the size appended after a pipe (e.g. '/path/to/file|10G'). The file will be created if necessary and be mapped to a loopback device. This is intended for development and testing purposes. The default size is 5G.

To prevent potential data loss an already formatted device (or one containing LVM metadata) cannot be used unless the overwrite configuration option is set to 'true'.


Comma-separated list of key=value configuration flags. These will be added to Cinder's cinder.conf file and will only affect the LVM backend.


Permits (with a value of 'true') the charm to attempt to overwrite storage devices (specified by the block-devices option) if they contain pre-existing filesystems or LVM metadata. The default is 'false'. A device in use on the host will never be overwritten.


Specify a block device (here we choose /dev/sdb) and then add a relation to the cinder charm:

juju deploy --config block-device=sdb cinder-lvm
juju add-relation cinder-lvm:storage-backend cinder:storage-backend


The OpenStack Charms project maintains two documentation guides:


Please report bugs on Launchpad.