openstack/puppet-congress
Code Issues Proposed changes
RETIRED, OpenStack Congress Puppet Module
161 Commits 1 Branch 46 Tags 1.8 MiB
ab8a734de2
Go to file
Alex Schultz ab8a734de2 Prepare Rocky RC1 
Update the version metadata for Rocky RC1

Change-Id: Ifc20d64a7220a2b3a38615ccbc37c5033ff0ca42
2018-08-14 08:56:51 -06:00
doc Follow the new PTI for document build 2018-02-28 14:42:10 +08:00
lib/puppet Add api_paste type/provider for congress 2017-07-26 11:31:56 +08:00
manifests Fix annotations 2018-06-15 15:07:37 +08:00
releasenotes Remove deprecated parameters 2018-05-21 23:04:13 +02:00
spec modulesync: sync and add nodepool-bionic for beaker 2018-07-18 16:17:31 +02:00
tests Fix the smoke testing link 2018-07-30 12:31:32 -04:00
.gitignore Update .gitignore 2018-04-11 08:55:13 +08:00
.gitreview Commiting a cookie cutter module sync set of files 2016-06-14 11:47:20 -04:00
.zuul.yaml Zuul: Remove project name 2018-01-29 02:20:51 +08:00
bindep.txt modulesync: sync and add nodepool-bionic for beaker 2018-07-18 16:17:31 +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:10 +08:00
metadata.json Prepare Rocky RC1 2018-08-14 08:56:51 -06:00
Rakefile Commiting a cookie cutter module sync set of files 2016-06-14 11:47:20 -04:00
README.md Remove the unnecessary _ 2018-07-24 23:53:03 +08:00
setup.cfg Update URLs in documents according to document migration 2017-07-14 08:51:20 +08:00
setup.py Add basic structure for ReNo 2016-10-07 15:01:30 +00:00
tox.ini fix tox python3 overrides 2018-06-08 14:23:32 +08: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

Release Notes

Repository