openstack/sunbeam-charms
Code Issues Proposed changes
0bdc19c4ea
sunbeam-charms/charms/cinder-k8s
History
Guillaume Boutry e911599abe
Migrate to unified charmcraft.yaml 
Charmcraft 3 moves towards a single charmcraft.yaml, this is needed for
24.04 migration.

Change-Id: I743712752aaf37bf68730b64bd6c147dfad370e2
Signed-off-by: Guillaume Boutry <guillaume.boutry@canonical.com>
2024-10-08 09:38:10 +02:00
..
lib/charms/cinder_k8s/v0 [ops-sunbeam] Implement mypy linter 2024-08-13 18:56:33 +02:00
src [*] update charm entrypoints 2024-10-07 11:11:43 +02:00
tests Migrate to unified charmcraft.yaml 2024-10-08 09:38:10 +02:00
.gitignore Refactor monorepo build-system 2024-07-08 21:51:09 +02:00
.sunbeam-build.yaml Implement tracing 2024-07-31 11:57:32 +02:00
build-requirements.txt Switch to using aso 2021-10-12 13:27:22 +01:00
charmcraft.yaml Migrate to unified charmcraft.yaml 2024-10-08 09:38:10 +02:00
CONTRIBUTING.md Update for 2024.1 2024-04-18 23:21:03 +00:00
LICENSE charm init 2021-09-23 09:32:42 +01:00
README.md Update for 2024.1 2024-04-18 23:21:03 +00:00
rebuild Allow rebuild charms on modifying a rebuild file 2023-12-06 18:58:50 +01:00
requirements.txt Remove upper contraints on pydantic 2024-08-27 14:06:38 +05:30

README.md

cinder-k8s

Description

cinder-k8s is an operator to manage the Cinder API and Scheduler services on a Kubernetes based environment.

Usage

Deployment

cinder-k8s is deployed using below command:

juju deploy cinder-k8s cinder --trust

Now connect the cinder operator to existing database, messaging and keystone identity operators:

juju relate mysql:database cinder:database
juju relate rabbitmq:amqp cinder:amqp
juju relate keystone:identity-service cinder:identity-service

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 cinder. If the charm is not deployed then see file actions.yaml.

Relations

cinder-k8s requires the following relations:

database: To connect to MySQL amqp: To connect to RabbitMQ identity-service: To register endpoints in Keystone ingress-internal: To expose service on underlying internal network ingress-public: To expose service on public network storage-backend: To connect to backends which manage block storage

OCI Images

The charm by default uses follwoing images:

ghcr.io/canonical/cinder-api:2024.1 ghcr.io/canonical/cinder-scheduler: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.