5048222e3d
All OpenStack Charms now contain identical tox.ini files, not to be modified or made unique within each charm repo. This is to ensure consistency across charm repos in tox target naming, approach and purpose, also giving the charm dev and test experience additional consistency. Also create empty dirs with .keep files where necessary. Some classic charms have actions and/or lib dirs, and some do not. In all classic charms, flake will now check those dirs to ensure lint coverage of existing or future content. Rename bespoke amulet smoke test file name to standard. Change-Id: I0ddef0f8bc000581fc8369e0b837c580b44e6a78 |
||
---|---|---|
.. | ||
actions | ||
lib | ||
reactive | ||
templates/mitaka | ||
tests | ||
HACKING.md | ||
README.md | ||
actions.yaml | ||
config.yaml | ||
layer.yaml | ||
metadata.yaml | ||
test-requirements.txt | ||
tox.ini |
README.md
Overview
This charm provides the Barbican secret service for an OpenStack Cloud.
Usage
Barbican relies on services from the mysql/percona, rabbitmq-server and keystone charms:
juju deploy barbican
juju deploy keystone
juju deploy mysql
juju deploy rabbitmq-server
juju add-relation barbican rabbitmq-server
juju add-relation barbican mysql
juju add-relation barbican keystone
Optionally, but advisedly, Barbican should be deployed with an HSM subordinate charm.
Bugs
Please report bugs on Launchpad.
For general questions please refer to the OpenStack Charm Guide.