openstack
/
charm-cinder-k8s
Code Issues Proposed changes
Juju K8S Charm - Cinder
102 Commits
6 Branches
0 Tags
485 KiB
Python 95.9%
Jinja 3.5%
Shell 0.6%
 
 
 
Go to file
Guillaume Boutry a359931b25
Migrate traefik ingress to v2 
Current ingress relation only routes unit to requirer's leader.
Ingress V2 fixes that issue.

Change-Id: I5c4a64676360b59ad87ee505064be6ef6a84e90a
 		2023-09-26 17:41:17 +02:00
lib/charms Migrate traefik ingress to v2 2023-09-26 17:41:17 +02:00
src Request quorum queues 2023-09-25 10:29:36 +00:00
tests Request quorum queues 2023-09-25 10:29:36 +00:00
.flake8 charm init 2021-09-23 09:32:42 +01:00
.gitignore Restore libs 2021-10-15 11:41:02 +01:00
.gitreview Remove references to old github 2022-08-04 15:54:19 +05:30
.jujuignore charm init 2021-09-23 09:32:42 +01:00
.stestr.conf Sync global tox, requirement files 2022-07-27 12:54:14 +05:30
.zuul.yaml Re-enable functional tests 2023-08-29 13:15:31 +00:00
CONTRIBUTING.md Switch to Antelope 2023-05-24 18:22:01 +00:00
LICENSE charm init 2021-09-23 09:32:42 +01:00
README.md Switch to Antelope 2023-05-24 18:22:01 +00:00
actions.yaml Initial boilerplate updates 2021-09-23 09:46:09 +01:00
build-requirements.txt Switch to using aso 2021-10-12 13:27:22 +01:00
charmcraft.yaml Migrate traefik ingress to v2 2023-09-26 17:41:17 +02:00
config.yaml Initial boilerplate updates 2021-09-23 09:46:09 +01:00
fetch-libs.sh Migrate traefik ingress to v2 2023-09-26 17:41:17 +02:00
metadata.yaml Add 'extra' test dep 2023-09-18 11:46:32 +00:00
osci.yaml Switch to Antelope 2023-05-24 18:22:01 +00:00
pyproject.toml General tidy for charm 2023-01-19 08:25:20 +00:00
rename.sh Add osci yaml 2022-09-08 16:49:13 +05:30
requirements.txt Migrate traefik ingress to v2 2023-09-26 17:41:17 +02:00
test-requirements.txt Add 'extra' test dep 2023-09-18 11:46:32 +00:00
tox.ini General tidy for charm 2023-01-19 08:25:20 +00:00

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/openstack-snaps/cinder-api:2023.1 ghcr.io/openstack-snaps/cinder-scheduler:2023.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.