openstack/puppet-zaqar
Code Issues Proposed changes
OpenStack Zaqar Puppet Module.
56 Commits 7 Branches 103 Tags 4.7 MiB
Puppet 48.1%
Ruby 46.4%
Python 5.5%
cbc5c8b2fe
Go to file
Andreas Jaeger cbc5c8b2fe Move other-requirements.txt to bindep.txt 
The default filename for documenting binary dependencies has been
changed from "other-requirements.txt" to "bindep.txt" with the release
of bindep 2.1.0. While the previous name is still supported, it will
be deprecated.

Move the file around to follow this change.

Note that this change is self-testing, the OpenStack CI infrastructure
will use a "bindep.txt" file to setup nodes for testing.

For more information about bindep, see also:
http://docs.openstack.org/infra/manual/drivers.html#package-requirements
http://docs.openstack.org/infra/bindep/

As well as this announcement:
http://lists.openstack.org/pipermail/openstack-dev/2016-August/101590.html

Change-Id: I35206e22a64e576e77a34dcccdc6835c40d73a72
2016-08-12 21:13:27 +02:00
lib/puppet Reflect provider change in puppet-openstacklib 2016-02-11 20:10:48 -05:00
manifests Move authtoken to class 2016-08-04 12:25:34 -03:00
releasenotes Move authtoken to class 2016-08-04 12:25:34 -03:00
spec Move authtoken to class 2016-08-04 12:25:34 -03:00
templates Add zaqar::server_instance class. 2016-02-17 08:23:57 -05:00
tests puppet-zaqar: Initial commit 2015-08-25 09:59:38 -07:00
.gitignore Add basic structure for ReNo 2016-03-14 08:37:01 -04:00
.gitreview Added .gitreview 2015-06-17 21:29:20 +00:00
bindep.txt Move other-requirements.txt to bindep.txt 2016-08-12 21:13:27 +02:00
CHANGELOG.md Release 8.0.0 2016-03-23 16:08:03 -04:00
Gemfile Gemfile: rely on puppet-openstack_spec_helper for dependencies 2016-03-29 21:37:45 -04:00
LICENSE puppet-zaqar: Initial commit 2015-08-25 09:59:38 -07:00
metadata.json Prepare 9.1.0 (newton-2) 2016-07-07 09:10:32 -04:00
Rakefile Use puppet-openstack_spec_helper for Rakefile & spec_helper_acceptance 2016-01-18 09:11:37 -05:00
README.md Change wiki to docs 2016-06-02 23:46:19 -03:00
setup.cfg Add basic structure for ReNo 2016-03-14 08:37:01 -04:00
setup.py Add basic structure for ReNo 2016-03-14 08:37:01 -04:00
test-requirements.txt Add basic structure for ReNo 2016-03-14 08:37:01 -04:00
tox.ini Add basic structure for ReNo 2016-03-14 08:37:01 -04:00

README.md

zaqar

Table of Contents

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

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.

Types

zaqar_config

The zaqar_config provider is a children of the ini_setting provider. It allows one to write an entry in the /etc/zaqar/zaqar.conf file.

zaqar_config { 'DEFAULT/debug' :
  value => true,
}

This will write debug=true in the [DEFAULT] section.

name

Section/setting name to manage from zaqar.conf

value

The value of the setting to be defined.

secret

Whether to hide the value from Puppet logs. Defaults to false.

ensure_absent_val

If value is equal to ensure_absent_val then the resource will behave as if ensure => absent was specified. Defaults to <SERVICE DEFAULT>

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.

Contributors