OpenStack Barbican Puppet Module
Go to file
ZhongShengping 6e55ffba30 Dissuade .gitignore references to personal tools
Developers run all sorts of different tools within Git repositories,
any of which can leave their own special trashfiles all over the
place. We can't every hope to catalog them all, so better to
recommend developers simply configure a global core.excludesfile to
filter the irrelevant files which tend to get created by their
personal choice of tools. Add a comment block explaining this, for
clarity, and remove the one current editor-specific entry present.

We can, and should of course, continue to list files created by the
tools recommended by our workflow (test frameworks, documentation
and packaging builds, et cetera).

This change is a port of Ib58a57267b064e4142686de6c37a70dbff04b9a7
from the openstack-dev/cookiecutter repository.

Change-Id: Iae670be05658ca5c123fc9132d9253f6ee3d4b7d
2018-10-08 11:39:22 +08:00
doc Follow the new PTI for document build 2018-02-28 14:42:10 +08:00
lib/puppet Add missing license files 2016-09-20 00:29:00 -04:00
manifests Add barbican::worker class 2018-08-30 15:22:54 +02:00
releasenotes Add barbican::worker class 2018-08-30 15:22:54 +02:00
spec Add barbican::worker class 2018-08-30 15:22:54 +02:00
tests Fix the smoke testing link 2018-07-30 12:31:47 -04:00
.gitignore Dissuade .gitignore references to personal tools 2018-10-08 11:39:22 +08:00
.gitreview Added .gitreview 2015-10-01 07:52:35 +00:00
.zuul.yaml switch documentation job to new PTI 2018-08-31 08:24:32 -04:00
bindep.txt modulesync: sync and add nodepool-bionic for beaker 2018-07-18 16:17:07 +02:00
Gemfile Load puppet-openstack_spec_helper locally during tests 2018-02-12 10:53:34 +08:00
LICENSE Update LICENSE 2018-04-06 20:14:07 +08:00
metadata.json Bump version for the start of Stein 2018-08-30 12:08:48 -06:00
Rakefile Use puppet-openstack_spec_helper for Rakefile & spec_helper_acceptance 2016-01-18 09:11:12 -05:00
README.md Add the missing 'Table of Contents' 2018-08-27 14:10:18 +00:00
setup.cfg Change author in setup.cfg 2017-07-26 05:08:56 +00:00
setup.py Add basic structure for reno 2016-05-27 16:14:57 -04:00
tox.ini fix tox python3 overrides 2018-06-08 14:23:31 +08:00

Team and repository tags

Team and repository tags

barbican

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

Overview

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.

Setup

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.

Implementation

barbican

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

Limitations

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

Beaker-Rspec

This module has beaker-rspec tests

To run the tests on the default vagrant node:

bundle install
bundle exec rake acceptance

For more information on writing and running beaker-rspec tests visit the documentation:

Development

Developer documentation for the entire puppet-openstack project.

Release Notes

Contributors

Repository