openstack
/
puppet-congress
Code Issues Proposed changes
RETIRED, OpenStack Congress Puppet Module
13 Commits 1 Branch 46 Tags 1.8 MiB
Go to file
Iury Gregory Melo Ferreira 9cd38f460b Add basic structure for ReNo 
ReNo [1] is the release management tool in OpenStack.
This patch adds the basic structure to start using it.

* Update .gitignore
* Add releasenotes/ dir and basic files
* Add python files: setup.cfg, setup.py, test-requirements.txt and
  tox.ini.

[1] http://docs.openstack.org/developer/reno

Change-Id: I3fb6945c200db9fa53dab15ccee3e9e7f94ec2ba
 		2016-10-07 15:01:30 +00:00
lib/puppet Commiting a cookie cutter module sync set of files 2016-06-14 11:47:20 -04:00
manifests Populating init.pp and parameters 2016-09-30 09:57:09 -04:00
releasenotes/source Add basic structure for ReNo 2016-10-07 15:01:30 +00:00
spec Move rspec-puppet-facts to spec helper 2016-09-30 13:17:34 -06: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 Commiting a cookie cutter module sync set of files 2016-06-14 11:47:20 -04:00
Gemfile Commiting a cookie cutter module sync set of files 2016-06-14 11:47:20 -04:00
LICENSE Commiting a cookie cutter module sync set of files 2016-06-14 11:47:20 -04:00
README.md Commiting a cookie cutter module sync set of files 2016-06-14 11:47:20 -04:00
Rakefile Commiting a cookie cutter module sync set of files 2016-06-14 11:47:20 -04:00
metadata.json Fix authtoken 2016-08-27 00:50:44 -03:00
setup.cfg Add basic structure for ReNo 2016-10-07 15:01:30 +00:00
setup.py Add basic structure for ReNo 2016-10-07 15:01:30 +00:00
test-requirements.txt Add basic structure for ReNo 2016-10-07 15:01:30 +00:00
tox.ini Add basic structure for ReNo 2016-10-07 15:01:30 +00:00

README.md

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