Go to file
Emilien Macchi a49f187941 Try to use zuul-cloner to prepare fixtures
In OpenStack Infra, we would like to run Puppet unit tests that
sometimes depends on other Puppet OpenStack modules.
Example: a patch in puppet-openstacklib that needs to be tested in puppet-nova.

This patch modifies the Rakefile to:
* clean spec_prep and spec_clean Rake tasks
* use openstack/puppet-openstack-integration/install_modules_unit.sh script
  to clone modules.
* do not use .fixtures.yaml file to clone modules and rely on
  zuul-cloner or git.
* Add openstack/ in gitignore so we never commit the
  puppet-openstack-integration repository (can happen when spec_clean
  did not run but you want to submit the patch anyway)
* Allow to run a custom Puppetfile if PUPPETFILE env is exported. It
  will allow people to test the module with the dependencies they like,
  feature we had with .fixtures.yaml.

Also add 'r10k' to Gemfile.

That way, we will be able to use zuul dependencies and run tests accross
modules like we do with functional testing.

Change-Id: I4f5b3df5c00bca02af401fd458a20aaa07ee560d
2015-10-08 14:43:41 -07:00
2015-10-02 08:50:49 -04:00
2015-10-02 08:50:49 -04:00
2015-10-02 08:50:49 -04:00
2015-10-01 07:52:35 +00:00
2015-10-02 08:50:49 -04:00
2015-10-02 08:50:49 -04:00
2015-10-02 08:50:49 -04:00

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. 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 its self 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.

Contributors

Description
OpenStack Barbican Puppet Module
Readme 5.5 MiB
Languages
Ruby 54.8%
Puppet 38.8%
Python 3.8%
Pascal 2.6%