943c06f75a
This reverts commit ddd397bdc0.
Reason for revert: To avoid regression https://bugs.launchpad.net/snap-openstack/+bug/2126612
Additional change:
Install ops<3.x in test-requirements. This is a workaround and
will be fixed in subsequent PR to move test-requirements
to pyproject.toml so that charms as well as test environment
will use same tox version from uv.lock
Change-Id: I6f1e517e89de16908c876955a880c05581900366
Signed-off-by: Hemanth Nakkina <hemanth.nakkina@canonical.com>
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.