reno=2.0.0 breaks releasenotes test Change-Id: I484dc5a936950a00fb08a762f23670515b1b5494 Closes-Bug: #1651995
Team and repository tags
Table of Contents
- Overview - What is the panko module?
- Module Description - What does the module do?
- Setup - The basics of getting started with panko
- Implementation - An under-the-hood peek at what the module is doing
- Limitations - OS compatibility, etc.
- Development - Guide for contributing to the module
- Contributors - Those with commits
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.
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.
What the panko module affects
- Panko, the events service for OpenStack.
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.
panko is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.
- All the panko types use the CLI tools and so need to be ran on the panko node.
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:
Developer documentation for the entire puppet-openstack project.