Hemanth Nakkina
e07819a9d9
Currently each charm defines in the code all the mandatory relations. Instead populate the mandatory relations from chamrcraft.yaml requires relations with optional as False. Charm can define mandatory relations that are not derived from requires relations and they will be appended to the list of mandatory_relations. Barbican and ovn-central charms follows this pattern. Change-Id: Iff45fca33dc954593ded52b97e905431b6a7bb53
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.