Juju Charm - Cinder LVM backend
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
Felipe Reyes 404a6d652e Install charm-helpers from master branch 2 months ago
src Install charm-helpers from master branch 2 months ago
unit_tests Change config parameter 'backend-name' to 'volume-backend-name' 1 year ago
.gitignore Add *.charm to gitignore 8 months ago
.gitreview Curate the cinder-lvm charm 1 year ago
.stestr.conf Initial Cookiecutter Commit. 2 years ago
.zuul.yaml Add Kinetic and Zed support 3 months ago
README.md Curate the cinder-lvm charm 1 year ago
bindep.txt Add Kinetic and Zed support 3 months ago
build-requirements.txt Update to build using charmcraft 10 months ago
charmcraft.yaml Add kinetic to run-on 2 months ago
copyright Curate the cinder-lvm charm 1 year ago
metadata.yaml Curate the cinder-lvm charm 1 year ago
osci.yaml Add Kinetic and Zed support 3 months ago
pip.sh Curate the cinder-lvm charm 1 year ago
rename.sh Update to build using charmcraft 10 months ago
requirements.txt Add Kinetic and Zed support 3 months ago
test-requirements.txt Add Kinetic and Zed support 3 months ago
tox.ini Build separately for each supported series and use binary builds 2 months ago

README.md

Overview

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.

Usage

Configuration

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.

allocation-type

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'.

block-device

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'.

config-flags

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.

overwrite

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.

Deployment

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

Documentation

The OpenStack Charms project maintains two documentation guides:

Bugs

Please report bugs on Launchpad.