openstack
/
charm-interface-keystone-domain-backend
Code Issues Proposed changes
Charm Interface - Keystone Domain backend
3 Commits 1 Branch 0 Tags 97 KiB
Python 100%
Go to file
Andreas Jaeger fd44f9c73a Update tox to remove deprecated pip option 
The job --allow-unverified is obsolete, also python-apt cannot be
installed and is unneeded for current jobs.

Remove so that python installation works.

Change-Id: I0adff13bbf91f324de5762e04d75488ca47f1f36
 		2018-10-04 12:19:32 +02: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 Update tox to remove deprecated pip option 2018-10-04 12:19:32 +02: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.