Charm Interface - Cinder Backend
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Liam Young f772252bcb Remove copy/pasta errors in names in unit tests 5 months ago
unit_tests Remove copy/pasta errors in names in unit tests 5 months ago
.gitignore Add unit_tests and drive by assorted 5 months ago
.testr.conf Add unit_tests and drive by assorted 5 months ago
.travis.yml Add unit_tests and drive by assorted 5 months ago
README.md initial commit, fleshed out basic interface function, readme, etc 10 months ago
interface.yaml Add unit_tests and drive by assorted 5 months ago
provides.py Add unit_tests and drive by assorted 5 months ago
test-requirements.txt Add unit_tests and drive by assorted 5 months ago
tox.ini Add unit_tests and drive by assorted 5 months ago

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