df70e376ff
* Add sunbeam project template to run pep8, py3 tests * Add zuul.d/zuul.yaml to run pep8, py3, cover tests * Update charmcraft and requirements for each charm * Add global tox.ini to invoke fmt, pep8, py3, cover, build * Add gitreview file * Fix py3 test failures in ciner-ceph-k8s, glance-k8s, openstack-exporter * Add jobs for charm builds using files option so that job is invoked if files within the component are modified. Add charm builds to both check and gate pipeline. * Make function tests as part of global. Split the function tests into core, ceph, caas, misc mainly to accomodate function tests to run on 8GB. Add function tests as part of check pipeline. * Add zuul job to publish charms in promote pipeline Add charmhub token as secret that can be used to publish charms. Note: Charmhub token is generated with ttl of 90 days. * Run tox formatting * Make .gitignore, .jujuignore, .stestr.conf global and remove the files from all charms. * Make libs and templates global. Split libs to internal and external so that internal libs can adhere to sunbeam formatting styles. * Add script to copy common files necessary libs, config templates, stestr conf, jujuignore during py3 tests and charm builds. * Tests for keystone-ldap-k8s are commented due to intermittent bug LP#2045206 Change-Id: I804ca64182c109d16bd820ac00f129aa6dcf4496 |
||
---|---|---|
.. | ||
src | ||
tests | ||
actions.yaml | ||
build-requirements.txt | ||
charmcraft.yaml | ||
config.yaml | ||
CONTRIBUTING.md | ||
LICENSE | ||
metadata.yaml | ||
README.md | ||
requirements.txt |
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.