openstack
/
charm-interface-cinder-backend
Code Issues Proposed changes
Charm Interface - Cinder Backend
4 Commits 1 Branch 0 Tags 102 KiB
Python 100%
Go to file
Liam Young 4343977350 Use json for subordinate configuration. 
JSON encoding the subordinate config data is the preffered way to
pass it down the relation. This is supported by the corresponding
context https://github.com/juju/charm-helpers/blob/master/charmhelpers/contrib/openstack/context.py#L1272
and this is the approach cinder-ceph takes.
 		2019-01-15 08:12:54 +00:00
README.md initial commit, fleshed out basic interface function, readme, etc 2018-08-06 10:14:10 -04:00
interface.yaml initial commit, fleshed out basic interface function, readme, etc 2018-08-06 10:14:10 -04:00
provides.py Use json for subordinate configuration. 2019-01-15 08:12:54 +00:00

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