OpenStack Barbican Puppet Module
Go to file
Jiri Podivin af6c77b120 setuptools: Disable auto discovery
The latest release of setuptools 61.0 made a breaking change[1] and
because of this change 'pip install' fails with the following error.

error: Multiple top-level packages discovered in a flat-layout:
['lib', 'spec', 'manifests', 'releasenotes'].

Users that don't set 'packages', 'py_modules', or configuration'
are still likely to observe the auto-discovery behavior, which may
halt the build if the project contains multiple directories and/or
multiple Python files directly under the project root.

To disable auto discovery, one can do below in





Note is not used to install puppet modules. However it is used
to generate a release note, thus should be fixed.


Signed-off-by: Jiri Podivin <>
Change-Id: I063202f73cceab933b2036e036bdab458e671a28
(cherry picked from commit 111ea8b69d)
(cherry picked from commit 73b6ebbe9f)
2022-11-03 01:01:22 +09:00
doc Update sphinx to the latest version 2021-03-27 15:31:56 +08:00
examples Convert all class usage to relative names 2019-12-08 15:15:52 +01:00
lib/puppet Use anchor to require necessary packages 2020-05-04 02:19:32 +09:00
manifests Skip dependency on keystone endpoint if endpoint is not configured 2021-10-06 08:21:32 +00:00
releasenotes Merge "Add missing unit test for p11_crypto_plugin_always_set_cka_sensitive" 2021-03-26 04:45:51 +00:00
spec Set fixture paths for unit tests 2021-06-03 06:12:05 +00:00
.gitignore Dissuade .gitignore references to personal tools 2018-10-08 11:39:22 +08:00
.gitreview Update .gitreview for stable/wallaby 2021-04-01 09:11:43 +00:00
.zuul.yaml Add Puppet Litmus 2020-08-31 21:12:41 +02:00
CONTRIBUTING.rst [ussuri][goal] Add CONTRIBUTING.rst 2020-05-10 22:31:10 +02:00
Gemfile Use openstack_spec_helper from zuul checkout 2020-08-30 22:52:52 +02:00
LICENSE Update LICENSE 2018-04-06 20:14:07 +08:00 Add Puppet Litmus 2020-08-31 21:12:41 +02:00
Rakefile Use puppet-openstack_spec_helper for Rakefile & spec_helper_acceptance 2016-01-18 09:11:12 -05:00
bindep.txt modulesync: sync and add nodepool-bionic for beaker 2018-07-18 16:17:07 +02:00
metadata.json Prepare a new Wallaby release 2022-01-28 18:09:11 +09:00
setup.cfg Change openstack-dev to openstack-discuss 2018-12-02 18:19:29 +01:00 setuptools: Disable auto discovery 2022-11-03 01:01:22 +09:00
tox.ini Update TOX_CONSTRAINTS_FILE for stable/wallaby 2021-04-01 09:11:47 +00:00

Team and repository tags

Team and repository tags


Table of Contents

  1. Overview - What is the barbican module?
  2. Module Description - What does the module do?
  3. Setup - The basics of getting started with barbican
  4. Implementation - An under-the-hood peek at what the module is doing
  5. Limitations - OS compatibility, etc.
  6. Development - Guide for contributing to the module
  7. Release Notes - Release notes for the project
  8. Contributors - Those with commits
  9. Repository - The project source code repository


The barbican module is a part of OpenStack, an effort by the OpenStack infrastructure team to provide continuous integration testing and code review for OpenStack and OpenStack community projects not part of the core software. The module itself is used to flexibly configure and manage the Key management service for OpenStack.

Module Description

The barbican module is a thorough attempt to make Puppet capable of managing the entirety of barbican. This includes manifests to provision region specific endpoint and database connections. Types are shipped as part of the barbican module to assist in manipulation of configuration files.


What the barbican module affects

  • Barbican, the Key management service for OpenStack.

Installing barbican

barbican is not currently in Puppet Forge, but is anticipated to be added soon. Once that happens, you'll be able to install barbican with:

puppet module install openstack/barbican

Beginning with barbican

To utilize the barbican module's functionality you will need to declare multiple resources. The following is a modified excerpt from the openstack module. This is not an exhaustive list of all the components needed, we recommend you consult and understand the openstack module and the core openstack documentation.



barbican is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.


  • All the barbican types use the CLI tools and so need to be ran on the barbican node.


Developer documentation for the entire puppet-openstack project.

Release Notes