728609d5cf
The config templates have a typo (api_paste_confg) that went unnoticed since we were using the default paste file location. We'll go ahead and drop it since some of the projects have renamed it and we're using the default path anyway. The middleware tests will catch it if the paste pipeline is no longer applied. Change-Id: Ia736740ee6f2ccb0c86d4110c17d621f107a9a27 Signed-off-by: Lucian Petrut <lpetrut@cloudbasesolutions.com>
cinder-ceph-k8s
Description
The cinder-ceph-k8s is an operator to manage the Cinder service integration with Ceph storage backend on a Kubernetes based environment.
Usage
Deployment
cinder-ceph-k8s is deployed using below command:
juju deploy cinder-ceph-k8s cinder-ceph --trust
Now connect the cinder-ceph application to database, messaging and Ceph services:
juju relate mysql:database cinder-ceph:database
juju relate rabbitmq:amqp cinder-ceph:amqp
juju relate ceph-mon:ceph cinder-ceph:ceph
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-ceph-k8s requires the following relations:
amqp: To connect to RabbitMQ
ceph: To connect to Ceph storage backend
database: To connect to MySQL
OCI Images
The charm by default uses ghcr.io/canonical/cinder-volume:2025.1
Contributing
Please see the Juju SDK docs for guidelines on enhancements to this charm following best practice guidelines, and CONTRIBUTING.md for developer guidance.
Bugs
Please report bugs on Launchpad.