RETIRED, OpenStack Congress Puppet Module
Go to file
Emilien Macchi 8e73938669 Prepare for Ocata post release
Prepare the metadata configuration for a new Ocata release.
Also add missing bindep file.

Change-Id: Id153b7411fa436c4fd95c7ed27cc4dcb31086f9a
2018-01-17 16:45:57 -08:00
lib/puppet Commiting a cookie cutter module sync set of files 2016-06-14 11:47:20 -04:00
manifests Updating service name for Red Hat platform 2017-02-09 15:33:18 -05:00
releasenotes/source Prepare for Ocata post release 2018-01-17 16:45:57 -08:00
spec Updating service name for Red Hat platform 2017-02-09 15:33:18 -05:00
tests Initial Commit 2016-03-13 11:48:15 -04:00
.gitignore Add basic structure for ReNo 2016-10-07 15:01:30 +00:00
.gitreview Update .gitreview for stable/ocata 2017-02-10 17:27:42 +00:00
.zuul.yaml Run puppet-openstack-beaker-jobs 2017-12-28 17:11:05 +00:00
Gemfile Update Gemfile to pull spec_helper from stable/ocata 2017-04-24 11:41:29 -04:00
LICENSE Commiting a cookie cutter module sync set of files 2016-06-14 11:47:20 -04:00
README.md Show team and repo badges on README 2016-11-25 17:19:17 +01:00
Rakefile Commiting a cookie cutter module sync set of files 2016-06-14 11:47:20 -04:00
bindep.txt Prepare for Ocata post release 2018-01-17 16:45:57 -08:00
metadata.json Prepare for Ocata post release 2018-01-17 16:45:57 -08:00
setup.cfg Change author in setup.cfg 2016-11-29 18:58:17 +08:00
setup.py Add basic structure for ReNo 2016-10-07 15:01:30 +00:00
test-requirements.txt Pin reno version to reno>=0.1.1,!=2.0.0 2016-12-22 11:24:35 +00:00
tox.ini Add basic structure for ReNo 2016-10-07 15:01:30 +00:00

README.md

Team and repository tags

Team and repository tags

congress

Table of Contents

  1. Overview - What is the congress module?
  2. Module Description - What does the module do?
  3. Setup - The basics of getting started with congress
  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 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.

Contributors