|
|
||
|---|---|---|
| lib/puppet | ||
| manifests | ||
| spec | ||
| tests | ||
| .gitignore | ||
| .gitreview | ||
| Gemfile | ||
| LICENSE | ||
| metadata.json | ||
| Rakefile | ||
| README.md | ||
zaqar
Table of Contents
- Overview - What is the zaqar module?
- Module Description - What does the module do?
- Setup - The basics of getting started with zaqar
- 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
Overview
The zaqar 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 FIXME service for Openstack.
Module Description
The zaqar module is a thorough attempt to make Puppet capable of managing the entirety of zaqar. This includes manifests to provision region specific endpoint and database connections. Types are shipped as part of the zaqar module to assist in manipulation of configuration files.
Setup
What the zaqar module affects
Zaqar, the queue service for Openstack.
Installing zaqar
zaqar is not currently in Puppet Forge, but is anticipated to be added soon. Once that happens, you'll be able to install zaqar with:
puppet module install openstack/zaqar
Beginning with zaqar
Implementation
zaqar
zaqar is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.
Limitations
- All the zaqar types use the CLI tools and so need to be ran on the zaqar 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.