barbican

History

Kaitlin Farr cc5858c9ae Use Castellan's backend option instead of api_class

This is a mostely complete solution.  Ideally we could use the stevedore
entry point name 'barbican' instead of the full class name for cinder, but
I87926d6c95ac82b6f74c263c7441614f80348c1e needs to merge first.

Change-Id: I32ed528f585e790bc771473504ab7e4bfeb63de9

2017-09-26 12:42:06 -04:00

barbican-vagrant

Warning about tox not working in Vagrant setup

2016-01-08 19:14:45 +00:00

lib

Revert "Use devstack functions for deploying barbican-svc"

2017-08-08 22:39:11 +00:00

upgrade

Using openstack command

2017-06-29 11:21:44 +07:00

gate_hook.sh

Add flag to allow devstack to run on f26 in gate

2017-09-13 16:54:43 -06:00

local.conf.example

Update local.conf.example

2017-02-28 20:49:05 +00:00

plugin.sh

Use Castellan's backend option instead of api_class

2017-09-26 12:42:06 -04:00

README.md

Use the new Devstack external plugin method

2015-09-01 20:44:47 +00:00

settings

Revert "Use devstack functions for deploying barbican-svc"

2017-08-08 22:39:11 +00:00

README.md

This directory contains the Barbican DevStack plugin.

To configure Barbican with DevStack, you will need to enable this plugin and the Barbican service by adding one line to the local section of your local.conf file.

To enable the plugin, add a line of the form:

enable_plugin barbican <GITURL> [GITREF]

where

<GITURL> is the URL of a Barbican repository
[GITREF] is an optional git ref (branch/ref/tag).  The default is master.

For example

enable_plugin barbican https://git.openstack.org/openstack/barbican stable/liberty

For more information, see the "Externally Hosted Plugins" section of http://docs.openstack.org/developer/devstack/plugins.html