Charm Interface - Keystone Domain backend
18893a5c38
Publish releases packages map to principal charm Related-Bug: #1806111 Change-Id: I1d58e9735360a43f9d2d32d6aefe18d0e5a2937d |
||
|---|---|---|
| .gitignore | ||
| .gitreview | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| interface.yaml | ||
| LICENSE | ||
| provides.py | ||
| README.md | ||
| test-requirements.txt | ||
| tox.ini | ||
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}.connectedThe 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 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.