Charm Interface - Cinder Backend
Go to file
tushargite96 5d9280cdde Add Python3 charm jobs
Change-Id: I2c31bc9403ecb3d5981817848e7cc0962f06e591
2022-10-11 12:11:02 +00:00
unit_tests Use unittest.mock instead of mock 2020-06-09 16:43:16 +02:00
.gitignore Add unit_tests and drive by assorted 2019-01-15 15:36:46 +00:00
.gitreview Avoid pollution and false positives with tox.ini 2019-08-29 16:42:56 +01:00
.stestr.conf Switch from testr to stestr for unit tests 2021-02-10 10:24:56 +00:00
.travis.yml Add unit_tests and drive by assorted 2019-01-15 15:36:46 +00:00
.zuul.yaml Add Python3 charm jobs 2022-10-11 12:11:02 +00:00
README.md initial commit, fleshed out basic interface function, readme, etc 2018-08-06 10:14:10 -04:00
interface.yaml Add unit_tests and drive by assorted 2019-01-15 15:36:46 +00:00
provides.py Add method for publishing releases packages map 2021-03-24 15:31:45 +01:00
test-requirements.txt Switch from testr to stestr for unit tests 2021-02-10 10:24:56 +00:00
tox.ini Stop configuring install_command in tox. 2021-06-29 15:26:47 +05:30

README.md

Overview

Basic interface for sending Cinder subordinate backend configuration to principle Cinder charms.

Usage

Requires

This interface layer will set the following state:

  • {relation_name}.connected The relation is established, but the charm may not have provided any backend information.

For example, the subordinate would handle the cinder-backend.connected state with something like:

@when('cinder-backend.connected')
def configure_cinder(cinder_principal):
    config = {'api-endpoint': '1.2.3.4',
              'admin-username': 'admin',
              'admin-password': 'openstack',
              'api-version': '1.0'}
    cinder_principle.configure_principal(
      backend_name='my_backend', configuration=config)

Contact Information