openstack
/
puppet-zaqar
Code Issues Proposed changes
OpenStack Zaqar Puppet Module.
171 Commits 8 Branches 96 Tags 4.7 MiB
Puppet 48.1%
Ruby 46.4%
Python 5.5%
Go to file
ZhongShengping d2891b9670 Add 'openstack-db' tag to db-sync Exec resource 
In order to make easy orchestration on all OpenStack db-sync, add this
tag so people can use this tag in composition layer.
A use case it to set some orchestration to make sure MySQL Galera is
ready before running any Exec with this tag.

Change-Id: I468f796bc344f91510e977dd07cfd563174c66dd
Closes-Bug: #1755102
 		2018-03-12 16:33:11 +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 Add 'openstack-db' tag to db-sync Exec resource 2018-03-12 16:33:11 +08:00
releasenotes Add 'openstack-db' tag to db-sync Exec resource 2018-03-12 16:33:11 +08:00
spec Add 'openstack-db' tag to db-sync Exec resource 2018-03-12 16:33:11 +08: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
.zuul.yaml Zuul: Remove project name 2018-02-02 18:22:01 +00: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 puppet-zaqar: Initial commit 2015-08-25 09:59:38 -07:00
README.md Change tag link to the newest address 2017-08-03 10:51:45 +08:00
Rakefile Use puppet-openstack_spec_helper for Rakefile & spec_helper_acceptance 2016-01-18 09:11:37 -05:00
bindep.txt Add Puppet package to bindep, for module build 2017-10-27 13:17:43 -07:00
metadata.json Prepare for official Queens release 2018-02-19 12:44:29 -05: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 Follow the new PTI for document build 2018-02-28 14:42:13 +08: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.

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