Guillaume Boutry 93eabbfa72
Implement cinder-volume as a snap
This change includes cinder-volume and cinder-volume-ceph to manager the
cinder-volume service as snap that can be configured over multiple
backends.

Change-Id: Id520fc95710c8516aed5eae08cb20c8e54808cc7
Signed-off-by: Guillaume Boutry <guillaume.boutry@canonical.com>
2025-02-24 13:22:53 +01:00
..
2025-02-24 13:22:53 +01:00
2025-02-24 13:22:53 +01:00
2025-02-24 13:22:53 +01:00
2025-02-24 13:22:53 +01:00
2025-02-24 13:22:53 +01:00

cinder-volume

Description

The cinder-volume is an operator to manage the Cinder-volume service in a snap based deployment.

Usage

Deployment

cinder-volume is deployed using below command:

juju deploy cinder-volume

Now connect the cinder-volume application to database, messaging and Ceph services:

juju relate mysql:database cinder-volume:database
juju relate rabbitmq:amqp cinder-volume:amqp
juju relate keystone:identity-credentials cinder-volume:identity-credentials
juju relate cinder:storage-backend cinder-volume:storage-backend

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.

Actions

This section covers Juju actions supported by the charm. Actions allow specific operations to be performed on a per-unit basis. To display action descriptions run juju actions cinderceph. If the charm is not deployed then see file actions.yaml.

Relations

cinder-volume requires the following relations:

amqp: To connect to RabbitMQ database: To connect to MySQL identity-credentials: To connect to Keystone

Contributing

Please see the Juju SDK docs for guidelines on enhancements to this charm following best practice guidelines, and CONTRIBUTING.md for developer guidance.