availability zone is not set for LVM-only cinder-volumes service configs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Cinder Charm |
Triaged
|
Low
|
Unassigned |
Bug Description
Currently the cinder charm deployed with "enabled-
The use-case is local volumes for native replicated database storage while root disks are stored in ceph as opposed to having root disks and database storage on the same device.
LVM usage is not segregated into a separate storage backend charm - this has to be done in the cinder charm itself.
AZ information is exposed by Juju from the underlying provider.
Example cinder.conf keys:
https:/
cinder-
cinder-
cinder-
The target scenario is a cloud where cinder is used both with ceph-volume for Ceph and ceph-volume for LVM which is a combination of the two scenarios discussed here:
https:/
cat >cinder.yaml <<END
cinder:
# for ceph we still need a volume service deployed
enabled-
cinder-volume-lvm:
enabled-
# note that you can pre-create full-disk partitions in MAAS to
# work around https:/
# /dev/disk/
# not /dev/<disk> entries
block-device: /dev/disk/
overwrite: true
END
# used for API and purposes
juju deploy --config=
# used for cinder-volume and LVM only
juju deploy --config=
juju add-relation cinder percona-cluster
juju add-relation cinder rabbitmq-server # RPC for api, scheduler and cinder-volume
juju add-relation cinder keystone
juju add-relation cinder nova-cloud-
juju add-relation cinder-volume-lvm percona-cluster
# see https:/
juju add-relation cinder-volume-lvm rabbitmq-server # RPC
juju add-relation cinder cinder-ceph
# <ceph and relations here>
Changed in charm-cinder: | |
status: | New → Triaged |
importance: | Undecided → Low |