Charm Interface - Keystone Domain backend

Go to file

Doug Hellmann fc6178f57c fix tox python3 overrides We want to default to running all tox environments under python 3, so set the basepython value in each environment. We do not want to specify a minor version number, because we do not want to have to update the file every time we upgrade python. We do not want to set the override once in testenv, because that breaks the more specific versions used in default environments like py35 and py36. Change-Id: I5c830302c4ec1641e72427fa725cf8dfb30696ba Signed-off-by: Doug Hellmann <doug@doughellmann.com>		2018-10-04 12:42:59 +00:00
.gitignore	Initial cut of interface	2017-01-27 11:10:44 +00:00
.gitreview	Initial cut of interface	2017-01-27 11:10:44 +00:00
LICENSE	Add LICENSE file	2017-01-27 11:12:20 +00:00
README.md	Initial cut of interface	2017-01-27 11:10:44 +00:00
interface.yaml	Initial cut of interface	2017-01-27 11:10:44 +00:00
provides.py	Initial cut of interface	2017-01-27 11:10:44 +00:00
test-requirements.txt	Initial cut of interface	2017-01-27 11:10:44 +00:00
tox.ini	fix tox python3 overrides	2018-10-04 12:42:59 +00:00

README.md

Overview

This interface layer handles the communication with Keystone via the 'keystone-domain-backend' interface protocol.

Usage

Provides

The interface layer will set the following state:

{relation_name}.connected The relation is established.

For example:

from charms.reactive import when


@when('domain-backend.connected')
@when('configuration.complete')
def configure_domain(domain):
    domain.domain_name('mynewkeystonedomain')
    domain.trigger_restart()

Typically a domain backend charm should validate that that it has sufficient and good configuration for the domain backend, write its configuration to /etc/keystone/domains/keystone.<domain-name>.conf and then trigger a restart of keystone using the trigger_restart method of the inteface, supplying the domain name at this point in time as well.

The keystone charm will create the domain in the keystone database, mapping to the underlying domain configuration on disk.