2.7 KiB
Team and repository tags
congress
Table of Contents
- Overview - What is the congress module?
- Module Description - What does the module do?
- Setup - The basics of getting started with congress
- 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 congress 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 policy service for OpenStack.
Module Description
The congress module is a thorough attempt to make Puppet capable of managing the entirety of congress. This includes manifests to provision region specific endpoint and database connections. Types are shipped as part of the congress module to assist in manipulation of configuration files.
Setup
What the congress module affects
- Congress, the policy service for OpenStack.
Installing congress
congress is not currently in Puppet Forge, but is anticipated to be added soon. Once that happens, you'll be able to install congress with:
puppet module install openstack/congress
Beginning with congress
To utilize the congress module's functionality you will need to declare multiple resources.
Implementation
congress
congress is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.
Limitations
- All the congress types use the CLI tools and so need to be ran on the congress 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.