OpenStack Zaqar Puppet Module.
Go to file
ZhongShengping 881f1f5673 Dissuade .gitignore references to personal tools
Developers run all sorts of different tools within Git repositories,
any of which can leave their own special trashfiles all over the
place. We can't every hope to catalog them all, so better to
recommend developers simply configure a global core.excludesfile to
filter the irrelevant files which tend to get created by their
personal choice of tools. Add a comment block explaining this, for
clarity, and remove the one current editor-specific entry present.

We can, and should of course, continue to list files created by the
tools recommended by our workflow (test frameworks, documentation
and packaging builds, et cetera).

This change is a port of Ib58a57267b064e4142686de6c37a70dbff04b9a7
from the openstack-dev/cookiecutter repository.

Change-Id: I40740b511dba7d3823642bcdb803730fba533b90
2018-10-08 11:39:26 +08:00
doc Follow the new PTI for document build 2018-02-28 14:42:13 +08:00
lib/puppet Reflect provider change in puppet-openstacklib 2016-02-11 20:10:48 -05:00
manifests Replace port 35357 with 5000 2018-07-18 10:29:33 +02:00
releasenotes Update reno for stable/rocky 2018-08-20 18:45:00 +00:00
spec Merge "modulesync: sync and add nodepool-bionic for beaker" 2018-07-23 03:55:32 +00: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 Dissuade .gitignore references to personal tools 2018-10-08 11:39:26 +08:00
.gitreview Added .gitreview 2015-06-17 21:29:20 +00:00
.zuul.yaml switch documentation job to new PTI 2018-08-31 08:24:48 -04:00
bindep.txt modulesync: sync and add nodepool-bionic for beaker 2018-07-18 16:20:51 +02:00
CHANGELOG.md Release 8.0.0 2016-03-23 16:08:03 -04:00
Gemfile Load puppet-openstack_spec_helper locally during tests 2018-02-12 10:53:41 +08:00
LICENSE Update LICENSE 2018-04-06 20:18:37 +08:00
metadata.json Bump version for the start of Stein 2018-08-30 12:11:47 -06:00
Rakefile Use puppet-openstack_spec_helper for Rakefile & spec_helper_acceptance 2016-01-18 09:11:37 -05:00
README.md Remove the unnecessary _ 2018-07-25 00:42:03 +08:00
setup.cfg Update URLs in documents according to document migration 2017-07-14 13:52:59 +08:00
setup.py Add basic structure for ReNo 2016-03-14 08:37:01 -04:00
tox.ini fix tox python3 overrides 2018-06-08 14:23:33 +08:00

Team and repository tags

Team and repository tags

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 queue 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

Release Notes

Repository