History

Hemanth Nakkina bd057784d5

Make keystone as certificate transfer provider

Add functionality to keystone to act as a
certificate transfer provider.
Add actions to add, remove, list CA certs
to keystone.
Add Certificate Transfer requires handler
in ops_sunbeam. Update keystone_auth section
cafile option if certificate is available
in receive-ca-cert relation.
Update metadata.yaml for keystone and rest of
k8s charms.

Change-Id: I9c800e8f8a0c9197b195331be7b445bafe794780

2024-02-14 17:10:28 +05:30

src

Make keystone as certificate transfer provider

2024-02-14 17:10:28 +05:30

tests

Add zuuljobs

2023-11-30 15:32:39 +05:30

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

Add zuuljobs

2023-11-30 15:32:39 +05:30

config.yaml

Initial boilerplate updates

2021-09-23 09:46:09 +01:00

CONTRIBUTING.md

Switch charm to Bobcat

2023-10-05 15:45:30 +00:00

LICENSE

charm init

2021-09-23 09:32:42 +01:00

metadata.yaml

Make keystone as certificate transfer provider

2024-02-14 17:10:28 +05:30

README.md

Switch charm to Bobcat

2023-10-05 15:45:30 +00:00

rebuild

Allow rebuild charms on modifying a rebuild file

2023-12-06 18:58:50 +01:00

requirements.txt

Add zuuljobs

2023-11-30 15:32:39 +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:2023.2 ghcr.io/canonical/cinder-scheduler:2023.2

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.