4931ad53b9
Update charm base to ubuntu@24.04 for all k8s based charms. Deploying k8s charm is abstracted from the underlying host base, therefore we can already deploy next generation based charms. Change-Id: If8e8960a58a39f9978aaeec26ed4df4a2b690396 Signed-off-by: Guillaume Boutry <guillaume.boutry@canonical.com> |
||
|---|---|---|
| .. | ||
| lib/charms/cinder_ceph_k8s/v0 | ||
| src | ||
| tests/unit | ||
| .gitignore | ||
| .sunbeam-build.yaml | ||
| charmcraft.yaml | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| README.md | ||
| rebuild | ||
| requirements.txt | ||
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:2024.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.