openstack
/
puppet-panko
Code Issues Proposed changes
DEPRECATED, OpenStack Panko Puppet Module
92 Commits 1 Branch 64 Tags 2.3 MiB
Go to file
Harry Rybacki 475abab586 Configure *_domain_name to Default by default 
Keystone v2.0 API was removed so we have no choice but configuring
user_domain_name and project_domain_name otherwise it fallbacks to
Keystone v2.0 and it fails. This patch sets the default value so we make
sure Keystone v3 will be used out of the box for our users.

Change-Id: If065a7b4dea0026d9a4b1e28dbf3ba934b61aa53
 		2017-10-06 10:54:06 -04:00
examples Implement Panko Api service 2016-09-21 10:33:07 -04:00
lib/puppet Fix filename of api_paste.ini 2017-07-26 09:29:38 +08:00
manifests Configure *_domain_name to Default by default 2017-10-06 10:54:06 -04:00
releasenotes Configure *_domain_name to Default by default 2017-10-06 10:54:06 -04:00
spec add parameter to overwrite/add wsgi process options 2017-09-24 12:23:05 +02:00
tests puppet-panko: Initial commit 2016-08-25 11:30:54 -04:00
.gitignore Add basic structure for ReNo 2016-10-07 14:58:15 +00:00
.gitreview Added .gitreview 2016-08-25 15:10:15 +00:00
Gemfile puppet-panko: Initial commit 2016-08-25 11:30:54 -04:00
LICENSE puppet-panko: Initial commit 2016-08-25 11:30:54 -04:00
README.md Update to the latest address in README 2017-09-21 12:29:17 +08:00
Rakefile puppet-panko: Initial commit 2016-08-25 11:30:54 -04:00
bindep.txt Update tox configuration 2017-05-17 09:45:04 -06:00
metadata.json Update versions for Queens cycle 2017-08-25 19:33:45 +00:00
setup.cfg Update URLs in documents according to document migration 2017-07-14 08:54:09 +08:00
setup.py Add basic structure for ReNo 2016-10-07 14:58:15 +00:00
test-requirements.txt Update openstackdocstheme to latest version 2017-09-20 11:05:36 +08:00
tox.ini Add environment variable 2017-06-12 16:03:50 +08:00

README.md

Team and repository tags

Team and repository tags

panko

Table of Contents

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

Module Description

The panko module is a thorough attempt to make Puppet capable of managing the entirety of panko. This includes manifests to provision region specific endpoint and database connections. Types are shipped as part of the panko module to assist in manipulation of configuration files.

Setup

What the panko module affects

  • Panko, the events service for OpenStack.

Installing panko

panko is not currently in Puppet Forge, but is anticipated to be added soon.  Once that happens, you'll be able to install panko with:
puppet module install openstack/panko

Beginning with panko

To utilize the panko module's functionality you will need to declare multiple resources.

Implementation

panko

panko is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.

Limitations

  • All the panko types use the CLI tools and so need to be ran on the panko 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