openstack
/
puppet-zaqar
Code Issues Proposed changes
OpenStack Zaqar Puppet Module.
300 Commits 9 Branches 98 Tags 4.7 MiB
Puppet 48.1%
Ruby 46.4%
Python 5.5%
Go to file
ZhongShengping a86565c39a Set openstackdocs_auto_name to use 'project' as name 
Change-Id: Idc76a456d26b30ca3a6dc35187037e26ff5ced84
 		2020-09-16 11:05:06 +08:00
doc Switch to newer openstackdocstheme and reno versions 2020-06-02 15:04:52 +02:00
examples Convert all class usage to relative names 2019-12-08 23:26:05 +01:00
lib/puppet Use anchor to require necessary packages 2020-05-04 02:30:14 +09:00
manifests Change to relative include 2020-07-13 21:25:13 +02:00
releasenotes Set openstackdocs_auto_name to use 'project' as name 2020-09-16 11:05:06 +08:00
spec Add Puppet Litmus 2020-08-31 22:05:53 +02:00
templates Add zaqar::server_instance class. 2016-02-17 08:23:57 -05:00
.gitignore Dissuade .gitignore references to personal tools 2018-10-08 11:39:26 +08:00
.gitreview OpenDev Migration Patch 2019-04-19 19:40:07 +00:00
.zuul.yaml Add Puppet Litmus 2020-08-31 22:05:53 +02:00
CHANGELOG.md Release 8.0.0 2016-03-23 16:08:03 -04:00
CONTRIBUTING.rst [ussuri][goal] Add CONTRIBUTING.rst 2020-05-10 22:56:10 +02:00
Gemfile Use openstack_spec_helper from zuul checkout 2020-08-30 23:08:40 +02:00
LICENSE Update LICENSE 2018-04-06 20:18:37 +08:00
README.md Add Puppet Litmus 2020-08-31 22:05:53 +02:00
Rakefile Use puppet-openstack_spec_helper for Rakefile & spec_helper_acceptance 2016-01-18 09:11:37 -05:00
bindep.txt modulesync: sync and add nodepool-bionic for beaker 2018-07-18 16:20:51 +02:00
metadata.json Prepare Victoria M3 2020-09-08 09:18:04 +08:00
setup.cfg Change openstack-dev to openstack-discuss 2018-12-02 18:20:54 +01:00
setup.py Add basic structure for ReNo 2016-03-14 08:37:01 -04:00
tox.ini [ussuri][goal] Cleanup for python 2.7 drop 2020-02-15 21:00:31 -06:00

README.md

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.

Development

Developer documentation for the entire puppet-openstack project.

Contributors

Release Notes

Repository