openstack
/
puppet-congress
Code Issues Proposed changes
RETIRED, OpenStack Congress Puppet Module
194 Commits 1 Branch 46 Tags 1.8 MiB
Go to file
ZhongShengping c1e3f13bd7 Service_token_roles_required missing in the server config file 
Service_token_roles_required missing in the server config file which
allows backwards compatibility to ensure that the service tokens are
compared against a list of possible roles for validity.

Change-Id: I95abaa0720ad38378dadf6d97114ee4f255d9713
Closes-Bug: 1778198
 		2019-02-15 10:03:01 +08:00
doc Follow the new PTI for document build 2018-02-28 14:42:10 +08:00
examples Fix module structure 2018-12-12 11:29:10 +01:00
lib/puppet Add api_paste type/provider for congress 2017-07-26 11:31:56 +08:00
manifests Service_token_roles_required missing in the server config file 2019-02-15 10:03:01 +08:00
releasenotes Service_token_roles_required missing in the server config file 2019-02-15 10:03:01 +08:00
spec Service_token_roles_required missing in the server config file 2019-02-15 10:03:01 +08:00
.gitignore Dissuade .gitignore references to personal tools 2018-10-08 11:39:23 +08:00
.gitreview Commiting a cookie cutter module sync set of files 2016-06-14 11:47:20 -04:00
.zuul.yaml switch documentation job to new PTI 2018-08-31 08:24:34 -04: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
README.md Change wiki to docs 2019-02-13 10:31:05 +08:00
Rakefile Commiting a cookie cutter module sync set of files 2016-06-14 11:47:20 -04:00
bindep.txt modulesync: sync and add nodepool-bionic for beaker 2018-07-18 16:17:31 +02:00
metadata.json Merge "Use puppet 4 compatible mysql functions" 2019-02-11 20:53:00 +00:00
setup.cfg Change openstack-dev to openstack-discuss 2018-12-02 18:19:38 +01:00
setup.py Add basic structure for ReNo 2016-10-07 15:01:30 +00:00
tox.ini Update min tox version to 2.0 2018-10-16 11:40:17 +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