|
|
||
|---|---|---|
| doc | ||
| lib/puppet | ||
| manifests | ||
| releasenotes | ||
| spec | ||
| tests | ||
| .gitignore | ||
| .gitreview | ||
| .zuul.yaml | ||
| bindep.txt | ||
| Gemfile | ||
| LICENSE | ||
| metadata.json | ||
| Rakefile | ||
| README.md | ||
| setup.cfg | ||
| setup.py | ||
| tox.ini | ||
Team and repository tags
barbican
Table of Contents
- Overview - What is the barbican module?
- Module Description - What does the module do?
- Setup - The basics of getting started with barbican
- Implementation - An under-the-hood peek at what the module is doing
- Limitations - OS compatibility, etc.
- Development - Guide for contributing to the module
- Contributors - Those with commits
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.
- https://docs.openstack.org/puppet-openstack-guide/latest/ Release notes for the project can be found at: https://docs.openstack.org/releasenotes/puppet-barbican