caf0b11a4d
Due to a build problem with the reactive plugin, this change falls back
on overriding the steps and doing a manual build, but it also ensures
the CI system builds the charm using charmcraft. Changes:
- add a build-requirements.txt
- modify charmcraft.yaml
- modify osci.yaml
-> indicate build with charmcraft
- modify tox.ini
-> tox -e build does charmcraft build/rename
-> tox -e build-reactive does the reactive build
- modify bundles to use the <charm>.charm artifact in tests.
and fix deprecation warning re: prefix
- tox inception to enable tox -e func-test in the CI
Change-Id: I5f6f7c7e281202e44d2f13e7478d04b6fcb93016
|
||
|---|---|---|
| src | ||
| unit_tests | ||
| .gitignore | ||
| .gitreview | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| build-requirements.txt | ||
| charmcraft.yaml | ||
| copyright | ||
| metadata.yaml | ||
| osci.yaml | ||
| pip.sh | ||
| README.md | ||
| rename.sh | ||
| requirements.txt | ||
| test-requirements.txt | ||
| tox.ini | ||
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:
- OpenStack Charm Guide: for project information, including development and support notes
- OpenStack Charms Deployment Guide: for charm usage information
Bugs
Please report bugs on Launchpad.