openstack
/
charm-interface-keystone-domain-backend
Code Issues Proposed changes
Charm Interface - Keystone Domain backend
4 Commits 1 Branch 0 Tags 97 KiB
Python 100%
Go to file
Doug Hellmann c59f42e35d import zuul job settings from project-config 
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.

Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.

Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.

See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html

Change-Id: Ia287d2df93cd4515378b03150feed8560f6d2f9d
Story: #2002586
Task: #24317
 		2018-10-04 12:42:50 +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
.zuul.yaml import zuul job settings from project-config 2018-10-04 12:42:50 +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.